feat!: Stop parsing flags after tool name in shed run #13
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
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.
shed runno longer parses flags after the tool name. Previously flags were allowed to occur anywhere so shed couldn't tell which flags were meant for shed, and which ones were meant for the tool. As a result,--had to be used before tool flags which lead to a clumsy experience, ex:shed run stringer -- -type=Pill.Now
shed runwill stop parsing flags after the first non-flag argument, i.e. the tool name. So the previous example would now beshed run stringer -type=Pill.