fix: call object mapper with the expected class on 4.3 - #7796
Merged
soyuka merged 1 commit intoMar 13, 2026
Conversation
soyuka
force-pushed
the
4.3-object-mapper-post-correct-target
branch
from
March 13, 2026 11:08
02612b5 to
4ecaa5d
Compare
soyuka
force-pushed
the
4.3-object-mapper-post-correct-target
branch
from
March 13, 2026 11:12
4ecaa5d to
edc4a41
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
2 participants
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.
When the input DTO or the API resource has multiple mapping targets, during a POST request with ApiPlatform, provide the expected target to the objectMapper to ensure the correct mapping is used.
Same fix than #7795 but on 4.3.