Merged
Conversation
bca5ff2 to
93ef4ba
Compare
Contributor
|
ya, 'did you mean' is probably better. thanks! |
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.
Description
Currently, when Nushell encounters an unknown flag, it prints all options in the help string. This is pretty verbose and uses the
formatted_flagssignature method, which isn't used anywhere else. This commit refactors the parser to usedid_you_meaninstead, which only suggest one closest option or sends the user tohelpif nothing close is found.Release notes summary - What our users need to know
Improved error messages for misspelled flags
Previously, the help text for a missing flag would list all of them, which could get verbose on a single line:
The new error message only suggests the closest flag:
Closes #16418