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
"Did you mean" hint on wrong command or flag #895
Comments
Should be optional tho |
Good idea for a new feature. I always loved how |
I'd love this!!! |
Related to the conversation in #826, I'd like to propose we only consider this feature for |
Sounds good, I suggest to use a third party library to provide the necessary algorithms around it. |
I'm in strong agreement here! |
I found three main packages which all seem a bit unmaintained:
From an implementation perspective I tend to use the Jaro-Winkler distance to match the closet command/flag. To start with a clean state I added go module support to matchr: antzucaro/matchr#10 |
This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else. |
Closing this as it has become stale. |
This issue or PR has been bumped and is no longer marked as stale! Feel free to bump it again in the future, if it's still relevant. |
This issue has a PR here! => #977 |
This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else. |
Closing this as it has become stale. |
We could tell the user what the closest command or argument match is by calculating the levenshtein distance between them.
What to do you think?
The text was updated successfully, but these errors were encountered: