fix JAVA-5764 #1610
Open
fix JAVA-5764 #1610
Conversation
This file contains 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
|
@raffaeleflorio could you include a test case for the issue? |
|
@rozza I've just added the test case. The |
|
@rozza I also added the |
raffaeleflorio
force-pushed
the
main
branch
2 times, most recently
from
89f904e to
0e7dfd4
Compare
raffaeleflorio
force-pushed
the
main
branch
2 times, most recently
from
67731e5 to
0b34a9b
Compare
…ith the roundTrip one
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.
This PR is about the JAVA-5764 issue. It changes the
encodemethod by skipping the encode of a property if it's already encoded as the discriminator.