Repository navigation
fix(graphql): update existing object on nested input id - #8786
Merged
Merged
Conversation
The GraphQL ItemDenormalizer lost ItemNormalizerTrait in the normalizer/denormalizer split (api-platform#7713), so a nested input carrying an id created a new object instead of populating the existing one. Fixes api-platform#8785
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.
Since #7713 the GraphQL
ItemDenormalizerextendsAbstractItemNormalizerdirectly and no longer gets theid→OBJECT_TO_POPULATElogic ofItemNormalizerTrait, so a nested input with anidcreated a new object instead of updating the existing one (4.3 behaviour). The denormalizer uses the trait again, like the REST/JSON-LD/JSON:API ones, with an optional logger appended to the constructor.