Workaround for #[option(command)] usage parsing #187
Merged
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.
In some cases (namely
#[option(command)]
nested inside another struct) it isn't possible to retrieve usage information (i.e.Options::command_usage
returnsNone
).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.