Issue 16394: Fix uncompileable java client code from composed schema #16478
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 changes addresses the bug of the Java client generating uncompilable code described in this issue. This bug occurs when (1) A composed schema is used (2) The all of parent has a discriminator property that is an enum and (3) Default settings are used for the
library
configuration property, i.e., okhttp-gson, the default, is used.PR checklist
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.-- Note: No changes after running scripts --
For Windows users, please run the script in Git BASH.
master
(7.0.1 - patch release),7.1.x
(minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)