[Serializer] Fix PropertyNormalizer
with named serializers
#60091
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.
An alternative approach to #59627. The main issue is that
serializer.normalizer.property
isn't tagged withserializer.normalizer
, which, to my understanding, was intentional. SinceMimeMessageNormalizer
depends on it, the same instance ofPropertyNormalizer
(with the default named converter) is used for every named serializer.This PR checks the arguments of normalizers and registers a child definition for any argument that is an instance of
NormalizerInterface
and doesn't have theserializer.normalizer
tag.cc @ruudk