[5.5] Unify the exception response format when converting to JSON #19333
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.
Currently any normal Exception is converted to this JSON structure:
In case debug mode is on, several other attributes appear (file, line, & trace).
However there are two exceptions to this structure, first a validation exceptions returns the following:
And an
AuthenticationException
returns:In this PR I'm attempting to unify the error response by returning the following from a validation exceptions:
If that PR is approved I'm going to change the response format in https://github.com/laravel/laravel/blob/develop/app/Exceptions/Handler.php#L55 as well, this will make it standard across the framework to have a
message
attribute in a JSON error response that consumers can use to render a message to the end user or log it somewhere for later.