[ObjectMapper] Correctly manage constructor initialization #61036
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.
Currently the ObjectMapper cannot support empty constructor initialization, which is particularly useful for Doctrine collections:
This kind of error is thrown by the PropertyAccessor:
This PR fixes this but also another related issue (#60807): since an "empty" (no constructor arguments) constructor is always called, the class-level transformation test does not pass anymore:
To solve this, a check is done on
map?->transform
.