-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
remove unnecessary bool enums #12192
Conversation
Hi, @iscai-msft Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
Swagger Generation Artifacts
|
Hi @iscai-msft, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iscai-msft We do have a LintRule R3018 EnumInsteadOfBoolean to encourage defining boolean as enum.
interesting @leni-msft, wasn't aware of that. However, the rule does state that you should only make it an enum if there will be more than 2 values possible. Since this is just
|
@NarayanThiru, please help review the changes for |
Hey @iscai-msft, why this change must be made now? I don't understand what tool/process is breaking/broken and why it cannot handle enums - can you explain? Since this is a breaking change, do I own the breaking change process to get this approved? We have our GA release in <2 months and are focused on that - so I cannot take up any additional work. Actually, can this wait for a few weeks? Asking, since I will be creating a new api-version for GA - end of Jan/early Feb, and can include this change as part of that. |
@iscai-msft I have already made changes to those files in these commits: |
@NarayanThiru boolean enums do not work in python as a language, so Python code is broken here. It might also cause issues in other languages. @roytan-microsoft it looks lke your PRs don't contain fixes for |
@iscai-msft EnableHelmOperatorDefinition is not under the MixedReality namespace. For the mixedreality change, it should be a noop for us, so I'm ok with that. |
@roytan-microsoft i'll remove the mixed reality code from this pr as you'll merge the code yourself. My apologies, I thought you also worked in the kubernetes namespace. thanks! |
no point in having these bool enums, also causing issues in generated code
see Azure/autorest.python#847 for generated code issue