-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Description() doesn't work for sub commands #139
Comments
Yes, it's true. It is a significant shortcoming of the API. Thank you for investigating it. I need to find time to develop an API that can support this. |
Fixed in #156 |
I was looking at this, and the main issue seems to be that description exists on Moving the field is fairly easy, but then we still need to populate to it somehow. This means we'd probably need to do it in I can get to the method with If that can be made to work, then the output of the if p.cmd.description != "" {
fmt.Fprintln(w, p.cmd.description)
} Epilogue can probably be made to work the same way, so those too would be per command instead of global on the parser. |
Description() defined for subcommands is not used for help text.
I think only root arg is considered.
parse.go line 232:
The text was updated successfully, but these errors were encountered: