Repository navigation
fix(serializer): read the current relation for deep_object_to_populate - #8825
Merged
soyuka merged 2 commits intoNov 12, 2026
Merged
Conversation
Maxcastel
marked this pull request as ready for review
November 9, 2026 08:58
soyuka
changed the title
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 symfony/symfony#67883,
deep_object_to_populateonly reads the current value of typed attributes. Our item normalizer types attributes itself and gives Symfony no type extractor, so on PATCH a nested object is now created instead of updated:PatchTest::testPatchRelationfails in CI on Symfony dev and Symfony 8.1.The normalizer now reads it itself, for the attributes typed in our metadata.