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

Workaround for #[option(command)] usage parsing #187

Merged
merged 1 commit into from
Jan 12, 2020

Conversation

tony-iqlusion
Copy link
Member

In some cases (namely #[option(command)] nested inside another struct) it isn't possible to retrieve usage information (i.e. Options::command_usage returns None).

This may be indicative of a bug in gumdrop, but regardless, when this occurs this handles the situation gracefully (usage info unavailable for that subcommand) rather than panicking.

In some cases (namely `#[option(command)]` nested inside another struct)
it isn't possible to retrieve usage information (i.e.
`Options::command_usage` returns `None`).

This may be indicative of a bug in `gumdrop`, but regardless, when this
occurs this handles the situation gracefully (usage info unavailable for
that subcommand) rather than panicking.
@tony-iqlusion tony-iqlusion merged commit ab6af5f into develop Jan 12, 2020
@tony-iqlusion tony-iqlusion deleted the usage-parsing-workaround branch January 12, 2020 16:14
@tony-iqlusion tony-iqlusion mentioned this pull request Jan 12, 2020
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

Successfully merging this pull request may close these issues.

None yet

1 participant