Updating TypeInfoAnnotation for Java generators #805
Merged
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
…mappings correctly
JoaoMMorgado
approved these changes
Nov 16, 2020
nreverendo
approved these changes
Nov 17, 2020
|
@HugoMario would you mind taking a look at this? Cheers! |
|
@HugoMario sorry for being persistent, but this is almost 4 months old 😄 |
Merged
|
thanks a lot for this PR @helderdiniz , and sorry for this long delay |
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.
Making
typeInfoAnnotation.mustacheof other Java generators consistent with Spring generator, in order to correctly interpretdiscriminatormapping.Related to issue #804