[Java][jaxrs-spec] Fix generated JsonTypeName when using underscore in schema names#23689
Open
BB223 wants to merge 1 commit intoOpenAPITools:masterfrom
Open
[Java][jaxrs-spec] Fix generated JsonTypeName when using underscore in schema names#23689BB223 wants to merge 1 commit intoOpenAPITools:masterfrom
JsonTypeName when using underscore in schema names#23689BB223 wants to merge 1 commit intoOpenAPITools:masterfrom
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
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.
Description
When using underscores in schema names and using discriminator mappings, the
JsonTypeNamewasn't correctly generated. This fixes the issue I mentioned in #10822The
namefield inCodegenModeland themodelNamefield inCodegenDiscriminator.MappedModelare not equal when using underscores. TheCodegenDiscriminator.MappedModelfield uses the sanitized name, which is equal to theclassnamefield ofCodgenModel. I don't know if the non equality is intended or not, since from the naming of the fields i would also assume they would be equal. I opted for using the rawschemaNamein both classes to check for equality.Open Question
When i added the undescores in the test file, the jaxrs-cxf-cdi sample suddenly included the
JsonTypeNameimport. I couldn't figure out why this is happening. It would be great, if someone could help me avoid this unused import.@bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @martin-mfg (2023/08)
PR checklist
Commit all changed files.
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*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)"fixes #123"present in the PR description)Summary by cubic
Fixes incorrect
@JsonTypeNamegeneration in the JAX-RS (jaxrs-spec) generator when schemas with underscores are used in discriminator mappings. Ensures the correct discriminator value by matching on raw schema names.JavaJAXRSSpecServerCodegen, comparemappedModel.schemaNametomodel.schemaNameto setx-discriminator-value.Dog_RequestinoneOfand mapping; regenerated sample addsJsonTypeNameimport inDogRequest.Written for commit dd89576. Summary will update on new commits.