-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Error on misspelled command is different #401
Comments
Thanks for reporting this! It does seem like we should handle invalid cases a bit better. |
I suspect that this will be handled better in the nextercism CLI, as we're using Cobra, which has some pretty snazzy help functionality. TODO: build a local version of the |
@tejasbubane would you see if this is handled better in https://github.com/exercism/cli/releases/tag/v3.0.0-alpha.2? |
@kytrinyx Yup, its better now. But I see two issues there:
|
Ah. We should use the binary name for this, rather than hard-coding Exercism. I'll fix that. The other thing is weird, I'm not sure why it's happening. It should definitely not show it twice, and it should also use the binary name rather than "". |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The main issue here seems to be fixed with improved error message: Should the duplication thing be moved to a separate issue? |
Yeah, would you mind opening a new issue for the duplication thing? I'll close this one. |
I misspelled the submit command and saw the error was a little different:
I think this can be handled in a better way - eg.
Invalid command <command name>
followed the entire help section.2.4.1
The text was updated successfully, but these errors were encountered: