[Serializer] Fix deserializing object collection properties #51369
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.
On Symfony <= 6.2 serializer versions the
supportsDenormalizationwas always called in\Symfony\Component\Serializer\Serializer::getDenormalizer.When the
getSupportedTypeslogic was introduced for Symfony 6.3 serializer someifstatement conditions were introduced and if they aretruethesupportsDenormalizationlogic is not called at all anymore. Those conditions currently prevent a legit use-case that worked prior to 6.3 from calling thesupportsDenormalizationmethod - the case being when the denormalizer is supposed to denormalize a collection/array of objects. This use-case still works even on the 6.3 serializer as long as the denormalizer does not implement the newgetSupportedTypesmethod, but that is triggering a deprecation.This PR aims to fix that so that denormalizing an array of objects still works even when using the new
getSupportedTypesmethod in a denormalizer.cc @tucksaun @nicolas-grekas