You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code is still there and works, and I remember a bit being made about it at the time on places like Laravel News. In my eyes, they are really nice features and helpful when starting new projects.
But is there a reason they were removed from the documentation? And more in general, if something is removed from the documentation like this, is there some meaning behind it, or maybe more prioritising what is going into documentation over other stuff so it doesn't get too long or something? It seemed odd that preventLazyLoading() and preventSilentlyDiscardingAttributes()weren't removed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A while ago,
preventAccessingMissingAttributes()
andshouldBeStrict()
were removed from the documentation during 10.x.The code is still there and works, and I remember a bit being made about it at the time on places like Laravel News. In my eyes, they are really nice features and helpful when starting new projects.
But is there a reason they were removed from the documentation? And more in general, if something is removed from the documentation like this, is there some meaning behind it, or maybe more prioritising what is going into documentation over other stuff so it doesn't get too long or something? It seemed odd that
preventLazyLoading()
andpreventSilentlyDiscardingAttributes()
weren't removed.Beta Was this translation helpful? Give feedback.
All reactions