Preserve null boxed primitives roundtrip #179
Merged
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
…a -> js with null boxed will fail
laurgarn
changed the title
laurgarn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a java object contains has a boxed primitive field set to null and is serialized to Json with SKIP_NULL,
the current deserialization puts a 0/False in place of the null. So the roundtrip java -> js -> java is assured not be idempotent in this case.
The TestNullIntegerConstructor ensure(d/s) that this behaviour is "stable".
This pull request is a proposal to change this above described behaviour, without mitigation.