Skip to content
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? error responses #109

Closed
billygriffin opened this issue Nov 25, 2019 · 1 comment
Closed

Did you mean? error responses #109

billygriffin opened this issue Nov 25, 2019 · 1 comment

Comments

@billygriffin
Copy link
Contributor

We want this product to feel like a helpful guide and not make you think too much. To that end, we'd like to implement a "Did you mean [command]?" in the event of misspellings.

The initial version of this should not be interactive but the person will need to retype the command.

@billygriffin billygriffin created this issue from a note in The GitHub CLI (To do 📝) Nov 25, 2019
@probablycorey probablycorey moved this from To do 📝 to In progress 🚧 in The GitHub CLI Dec 9, 2019
@probablycorey probablycorey self-assigned this Dec 9, 2019
@probablycorey
Copy link
Contributor

probablycorey commented Dec 9, 2019

I've got two bits of good news.

  1. I spent some time studying string similarity algorithms and came up with some idea for how we can do this.
  2. BUT it turns out the basic functionality is already included in the CLI framework we are using!

So I'm going to close this unless I get objections about how this isn't good enough!

The GitHub CLI automation moved this from In progress 🚧 to Done 💤 Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
The GitHub CLI
  
Done 💤
Development

No branches or pull requests

2 participants