-
-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest matching arguments if the user mistypes #1210
Comments
What about cases of multiple argument that are mistyped or providing multiple arguments and just one is mistyped? How would that work? |
To what extent are we checking that a flag is a mistype and matches some arg/flag? How is the diff of closest matching flag evaluated? |
I feel that a warning for wrong arguments is enough. P.S.
|
We're just taking the very first argument into account. |
This is essentially an addition on top of what we already have onboard. Getting suggestions is definitely gonna add to the UX. |
Saw the repo. 👍 I think showing help with warning in case any invalid flag is supplied is sufficient feedback. #1051 |
How would that work with alias? -d or -c |
As of now it just checks for the fully qualified flag names ignoring aliases. #1211 |
Which is not ideal. If user passes a series of parameters and the last one is wrong, the feature would fail. It should check all the arguments |
In-fact the very first unknown argument. |
closing in regard to #1255 |
Is your feature request related to a problem? Please describe.
Say the user makes a typo,
webpack-cli --confgi
as of now he'll be greeted with a warning such that the respective argument is not recognized.Describe the solution you'd like
Suggest the nearest matching argument.
Describe alternatives you've considered
Levenshtein distance algorithm.
Additional context
The text was updated successfully, but these errors were encountered: