Add ability to parse flags to the end #814
Merged
Conversation
This file contains 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
mfridman
force-pushed
the
mf/parsing-flags
branch
from
ce14ed9
to
9fccc8f
Compare
mfridman
force-pushed
the
mf/parsing-flags
branch
from
9fccc8f
to
7028417
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quick PR to see whether this makes sense -- adding the ability to parse flags anywhere on the CLI.
Something that bugs me is the inability to set flags after positional arguments. E.g., sometimes I want to toss a
-v(verbose) flag at the end of a long command, but right now we're stuck having to add flags before all positional arguments.See Allowing flags anywhere on the CLI for rationale.