ux: give more verbose message for CLI typos#1182
Merged
jmartin-tech merged 1 commit intoNVIDIA:mainfrom Apr 25, 2025
Merged
Conversation
leondz
added
cli
jmartin-tech
approved these changes
Apr 25, 2025
Collaborator
jmartin-tech
left a comment
jmartin-tech
left a comment
There was a problem hiding this comment.
@leondz's love for emoji knows no bounds :-)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Mistyping something like a generator name gave a pretty cryptic message
Make this clear, suggest an action, and follow our CLI design language
Verification
List the steps needed to make sure this thing works
garak -m teset.Repeat -p phrasing,grandma- the output should make it clear that (a) a generator was the offending item (b) what the string was that led to the failure (c) there are a coupla of next steps