Repository navigation
Conversation
Symfony's error renderer hands a FlattenException to the JSON:API ErrorNormalizer, which delegated to the item normalizer and kept only a generated id. Build the error members from the FlattenException and run them through the same tail as the item path. Refs api-platform#8704
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
1 participant
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.
When an error is rendered by Symfony's error controller (
handle_symfony_errors: false, the default, or an operation with_api_error_handler: false), the JSON:APIErrorNormalizerreceived aFlattenExceptionand only kept a generated id, so 404/405 router errors had an empty error object. The members are now built from theFlattenExceptionand go through the same tail as the item path, so the 5.x stringstatuscast applies after merge-up.detailis the status text unless debug is on, same as Symfony'sProblemNormalizer.The top-level
typemember from #8704 is left as is here, its removal is a separate patch on main.