Skip to content
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

Request: Allow Fine-Grained Per-Component inheritance within server GUI for each command #210

Open
jeremyhouser-ms opened this issue Feb 22, 2023 · 1 comment
Assignees

Comments

@jeremyhouser-ms
Copy link
Contributor

When creating a new API which inherits from an old one, the help messages and defaults for switches are overridden by the help messages and defaults of the old API, though the rest of the CLI generated is the expected code generated from the new API spec.

I have provided a video to @kairu-ms of my process which arrived at this error

image

See above, expected in red vs old API spec in green.

@jeremyhouser-ms jeremyhouser-ms changed the title Command help and defaults fail to update Command switch help and defaults fail to update Feb 22, 2023
@jeremyhouser-ms jeremyhouser-ms changed the title Command switch help and defaults fail to update Request: Allow Fine-Grained Per-Component inheritance within server GUI for each command Feb 22, 2023
@jeremyhouser-ms
Copy link
Contributor Author

jeremyhouser-ms commented Feb 22, 2023

Updated the title after a discussion with Kai. This is expected behavior, but can drive inconsistencies. I have altered this issue to instead be a request:
Allow for fine-grained control of when command names, default values, help messages, and any other gui-driven values are inherited when generating a new api version with inheritence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants