feat: specify flag name in parse error message#589
Merged
mdonnalley merged 2 commits intooclif:mdonnalley/589from Jan 23, 2023
Merged
feat: specify flag name in parse error message#589mdonnalley merged 2 commits intooclif:mdonnalley/589from
mdonnalley merged 2 commits intooclif:mdonnalley/589from
Conversation
mdonnalley
requested changes
Jan 18, 2023
Contributor
|
@MichaelGoberling Thanks for the contribution - love the idea! I just made a couple of suggestions to clean up the implementation |
mdonnalley
approved these changes
Jan 19, 2023
mdonnalley
added a commit
that referenced
this pull request
Jan 23, 2023
* feat: specify flag name in parse errors * fix: impl. for specifying flag name in parse errors Co-authored-by: Michael Goberling <[email protected]>
This file contains hidden or 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.
We have use cases where we want to use the
minandmaxvalues for an integer flag (See PR here)It would be nice if the parsing error message included the flag it pertained to
Before
After