[Serializer] Fix unexpected type in denormalization errors when float|int union type used in constructor with non numeric string in form-data request #62003
+20
−0
Conversation
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
… constructor in xml
|
Hey! Thanks for your PR. You are targeting branch "6.4" but it seems your PR description refers to branch "6.4 for features / 6.4, 7.3 for bug fixes". Cheers! Carsonbot |
xabbuh
approved these changes
Oct 8, 2025
HypeMC
approved these changes
Oct 8, 2025
|
Thank you @d-mitrofanov-v. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Remake of broken pull request, sorry once again for that, that fixes getting empty types in expectedTypes of NotNormalizableValueException if constructor properties have int|float union types and request has form-data field with non numeric string