Throw an http exception so it doesn't get reported #5642
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.
WHY
BEFORE - What was wrong? What was happening before this PR?
Reported in Laravel-Backpack/docs#590
We throw a regular Exception, that developer would need to manually add to "dontReport" if they don't want their logs filled with Access exceptions.
AFTER - What is happening after this PR?
The
AccessDeniedException
will no longer report to the log system as it will be treated as an HttpException under the hood.HOW
How did you achieve that, in technical terms?
We throw an a copy of Laravel
AuthorizationException
that's already non-reported by Laravel. There reason we don't throw the Laravel directly and throw our "custom", is to avoid a BC. We can totally remove our custom exception in next major version.Is it a breaking change?
Nop.