You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
See above, expected in red vs old API spec in green.
The text was updated successfully, but these errors were encountered:
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
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
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.
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
See above, expected in red vs old API spec in green.
The text was updated successfully, but these errors were encountered: