-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[discussion] Consider reducing amount of global options #2556
Comments
👍 Thanks for opening this issue! The team will review the labels and make any necessary changes. |
+1 |
What about doing it one step further by completely eliminating global options and having generator's options only? Likely this will be less confusing to new users. (we do not allow multiple "generator" (-g) target so the global option is not that useful as it cannot be shared) |
I like that idea as well. I wonder if it might be possible to pass those options as if they're global options rather than additionalProperties and configOptions. |
Somewhat related to "Global Options", the CLI |
Let's try to clean this up one way or another for 5.1. |
I think we'll need to deprecate all the top-level properties in CLI and plugins for 5.0 and through at least 5.1.0 |
Description
A question was raised out of #2429. We have quite a few "global" options (those available across all generators), which either aren't relevant to or aren't supported by many generators.
Should we consider thinning out these global options, or more clearly identifier which options are supported by which generators?
Per #2429, we should also identify if there may be other options which exist in global options with sibling options only available in
additionalProperties
.openapi-generator version
Pre-4.0
cc @OpenAPITools/generator-core-team
The text was updated successfully, but these errors were encountered: