Add support for custom scoped route model bindings #307
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for custom scopes in route model bindings.
Laravel 7 added the ability to scope nested route model bindings on a specific attribute:
Ziggy already supports passing an object parameter and automatically detecting an
id
key if one is present:This PR adds support for passing an object as a parameter with a custom binding scope:
Similarly to the existing behaviour with
id
, this only works if there are no conflicting route parameter names, so the example above won't necessarily work if there is another parameter explicitly called justslug
.