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

Fix bug with bool flags on subcommands #58

Merged
merged 1 commit into from
Jan 14, 2020
Merged

Fix bug with bool flags on subcommands #58

merged 1 commit into from
Jan 14, 2020

Conversation

ethanmoffat
Copy link
Contributor

Fixes error for valid bool flags "expected a following arg for flag , but it did not exist"

The fix is to check flags on all nested subcommands when determining if a flag is a bool

This fixes issue #57

Fixes error for valid bool flags "expected a following arg for flag <flag>, but it did not exist"

The fix is to check flags on all nested subcommands when determining if a flag is a bool
@integrii
Copy link
Owner

Whoa. I'll test this tonight and merge if it looks good - I am surprised something like this snuck through tests. Thank you!

@integrii integrii merged commit 6407017 into integrii:master Jan 14, 2020
@integrii
Copy link
Owner

Looks great! Nice work finding the right place and way to solve this problem in the codebase on your first try. Flaggy's code isn't always easy to follow, being a large recursive string parser. Thanks!

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.

2 participants