fix(serializer): allow nullable to-many relations to normalize as null#8254
Merged
soyuka merged 1 commit intoJun 5, 2026
Merged
Conversation
A property typed as a nullable collection of resources (e.g. ?array<Foo> or Collection|null) raised UnexpectedValueException during normalization because getAttributeValue() rejected any non-iterable value, including null. The to-one branch already accepted null; mirror that behavior on the to-many branch and return null when the property is nullable and the value is null. Fixes api-platform#7050
763c386 to
c101ff1
Compare
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.
Summary
AbstractItemNormalizer::getAttributeValue()rejected any non-iterable value on a to-many branch withUnexpectedValueException('Unexpected non-iterable value for to-many relation.')— includingnull. A property typed as a nullable collection of resources crashed during normalization. The to-one branch already accepted null; mirror that behavior on to-many and return null when the property is nullable.Reproduction
A resource exposing
?Collection<Item> $items = nullcrashed when serialized withitemsset to null.Test plan
Fixes #7050