Add JSON exception rendering helper for API routes#60208
Open
LucasCavalheri wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a small DX improvement for API-first Laravel applications.
It introduces a new convenience method:
which internally configures exception rendering for
api/*routes using the existingshouldRenderJsonWhen(...)API.The
install:apicommand/stubs have also been updated to automatically enable JSON exception rendering for API routes in newly generated applications.This helps avoid a common source of confusion when testing API routes with tools such as Postman, Insomnia, or curl without manually sending the
Accept: application/jsonheader.The implementation is intentionally minimal and does not mutate the incoming request or alter existing
expectsJson()behavior.