Default handling for discriminators with undefined mapping #12513
Eagleshield
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
The OpenAPI Specification regarding discriminators does not indicate that a custom mapping for the propertyName field is necessary. Currently, leaving a discriminator without mapping results in an NPE if the DefaultCodegenConfig.java class is used. Is it not desired to have the expected default case mentioned in the documentation, the schema name, as a fallback for missing mapping?
Thanks for the consideration.
Beta Was this translation helpful? Give feedback.
All reactions