Add corresponding API operation ID to CLI docs JSON#1399
Open
david-crespo wants to merge 1 commit intomainfrom
Open
Add corresponding API operation ID to CLI docs JSON#1399david-crespo wants to merge 1 commit intomainfrom
david-crespo wants to merge 1 commit intomainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #875
Was messing with linking to API endpoints corresponding to forms in the console (oxidecomputer/console#3153) and realized it would be nice to just link to the API endpoint and then let the API doc link you to the CLI if you want. Turns out I made an issue for this two years ago.
This can absolutely be done without the
unstable-extapproach if you'd rather not, it's just neater with it — feels like the way it wants to be done. The alternative is using the command path to go find the correspondingCliCommandfor a given clapCommand.unstable-extseems relatively stable to me. It hasn't been mentioned in the release notes since August 2024. If they ever messed with it, it would be really easy to deal with.