[13.x] Fix register a custom rendering closure for OAuthServerException
#1763
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 30, 2024
hafezdivandari
changed the title
OAuthServerExceptionOAuthServerException
…ithub.com/hafezdivandari/passport into 12.x-fix-rendering-oauth-server-exception
Member
|
Thanks @hafezdivandari |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR laravel/framework#51968 has to be merged before this.
Fixes #1756
Overriding the
rendermethod on\Laravel\Passport\Exceptions\OAuthServerExceptioncauses issue when registering a custom rendering closure, because this method takes precedence over the registered custom closure.