-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
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
bugfix: emit enum in schema when used as list or map element #454
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexzielenski The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm What kind of changes were you thinking? Emitting additional validation information in the OpenAPI seems like a net positive to me. |
/hold cancel I meant that the code generator feels like it could use a refactor. It is very painful to add/maintain features |
kubernetes#454 caused new enums to be emitted which exposed this bug. Some enums are aliases of others and redeclare their enum cases. This change causes duplicate eunm cases to be ignored
kubernetes#454 caused new enums to be emitted which exposed this bug. Some enums are aliases of others and redeclare their enum cases. This change causes duplicate eunm cases to be ignored
kubernetes#454 caused new enums to be emitted which exposed this bug. Some enums are aliases of others and redeclare their enum cases. This change causes duplicate eunm cases to be ignored
fixes #450
Doing this I feel like we are getting closer to need a refactor since when we add a feature there is so much conditional code we end up missing spots. But I am wondering how tolerant we are of possibly changing the generated schema?
/assign @Jefftree