-
Notifications
You must be signed in to change notification settings - Fork 72
Enhanced docs gen to more closely match existing docs (legacy) #692
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
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5c14f7b
enriched docs gen model
prasek bbeee0d
address feedback
prasek 309bf35
move command enrichments to parse.go
prasek 5407933
enhanced docs gen to more closely match existing docs
prasek b45bcba
encode JSON examples to avoid mdx acorn rendering error
prasek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Great improvement here! The old code fails to handle a few edge cases with more complex subcommands.
How are
ParentandChildrenused? I only seeChildrenbeing used to checkif len(c.Children) == 0 {, and I don't see theParentinformation used anywhere. If that's the case, I feel like a simpler approach would be to keep aIsLeafCommandfromenrich.goand use that for this condition hereUh oh!
There was an error while loading. Please reload this page.
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.
@yuandrew Thanks!
Parentis used inEnrichCommands()for various things including settingChildrenon theParent. Are you thinking anIsLeafCommand()helper or something on theCommandstruct?Childrengivesdocs.gomore flexibility in how the docs are rendered, for example the more hierarchical docs gen style used in thistcldPR which we probably want to move to fortemporalat some point.