🚨 Laravel developers, you may or may not have heard of the shouldBeStrict() method of Laravel's Model. It’s a game-changer for enforcing strict rules that protect your app from unexpected bugs. 🔒
Want to learn how it can level up your development? 🤔
Keep reading! 🧵
Want to learn how it can level up your development? 🤔
Keep reading! 🧵
Comments
1️⃣ Prevents lazy loading
2️⃣ Prevents silently discarding attributes
3️⃣ Prevents accessing missing attributes
Let’s break down these behaviors one by one 👇
🔴 Before enabling strictness:
Relationships are loaded lazily, silently triggering N+1 queries.
🟢 After enabling preventLazyLoading():
Strict mode throws a LazyLoadingViolationException
🔴 Before enabling strictness:
Attributes not in fillable or guarded are silently discarded without any warning:
🟢 After enabling preventSilentlyDiscardingAttributes():
Strict mode throws a MassAssignmentException when undefined attributes are saved.
🔴 Before enabling strictness:
Accessing a non-existent attribute simply returns null with no error:
🟢 After enabling preventAccessingMissingAttributes():
Strict mode throws a MissingAttributeException when trying to access undefined attributes
This way, your development stays strict, but production is monitored without causing disruptions. 💡📋
Enforce strict rules, handle violations, and keep your code clean. Happy coding! 👨💻👩💻
#Laravel #PHP