[5.5] prevent policies from being too greedy #19120
Merged
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 was originally sent to 5.4 (#19106) and Taylor asked me to switch to 5.5
Description:
Policies are too greedy, and will not defer to the gates if they do not have a method that matches the requested ability.
Steps To Reproduce:
Let's assume a
App\Blog
, andApp\Policies\Blog
.and the following
AuthServiceProvider
:Currently if you tried to use this ability, you would get an
AuthorizationException
, because the method didn't exist and the Gate would returnfalse
.This is because the Gate would see an
App\Blog
passed as the first argument, and try to resolve the callback fromApp\Policies\BlogPolicy
.Solution
This PR makes sure the ability/method is callable on the policy, otherwise falls through to let the gate check for a matching ability, and then finally defaults to return
false
.All tests are passing, including an additional one for this situation.