We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using JAXRS-SPEC, the x-enum-varnames and x-enum-descriptions do not seem to work together.
7.10.0
type: integer format: int32 enum: - 1000 - 900 - 30 - 20 - 10 - 0 x-enum-descriptions: - 'UNEXPECTED ERROR' - 'REJECT' - 'REFER EXCEPTION' - 'REFER' - 'REFER OVERRIDE' - 'NONE' x-enum-varnames: - UNEXPECTED_ERROR - REJECT - REFER_EXCEPTION - REFER - REFER_OVERRIDE - NONE
Using the above YAML, I would expect the generated enum to look something like
public enum Severity { UNEXPECTED_ERROR(1000, "UNEXPECTED ERROR"), REJECT(900, "REJECT"), REFER_EXCEPTION(30, "REFER EXCEPTION"), REFER(20, "REFER"), REFER_OVERRIDE(10, "REFER OVERRIDE"), NONE(0, "NONE"); ... }
Whereas it is being generated as
public enum Severity { UNEXPECTED_ERROR(1000), REJECT(900), REFER_EXCEPTION(30), REFER(20), REFER_OVERRIDE(10), NONE(0); ... }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report Checklist
Description
When using JAXRS-SPEC, the x-enum-varnames and x-enum-descriptions do not seem to work together.
openapi-generator version
7.10.0
OpenAPI declaration file content or url
Generation Details
Steps to reproduce
Using the above YAML, I would expect the generated enum to look something like
Whereas it is being generated as
Related issues/PRs
Suggest a fix
The text was updated successfully, but these errors were encountered: