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
would resolve the category model first, and then resolve the post model to only include posts from the specified category model.
This feature breaks when we apply the HasSlug trait on the scoped model (Post in this case), and the scoping simply does not occur. There's no errors, it just injects the wrong model into the controller's parameters, as if it was not scoped.
The text was updated successfully, but these errors were encountered:
Laravel has a feature to scope bindings based on parent / child relationships, for example the following route
would resolve the category model first, and then resolve the post model to only include posts from the specified category model.
This feature breaks when we apply the HasSlug trait on the scoped model (Post in this case), and the scoping simply does not occur. There's no errors, it just injects the wrong model into the controller's parameters, as if it was not scoped.
The text was updated successfully, but these errors were encountered: