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

Non-existent command returns confusing error #45

Closed
WesCossick opened this issue Mar 8, 2019 · 1 comment · Fixed by #60
Closed

Non-existent command returns confusing error #45

WesCossick opened this issue Mar 8, 2019 · 1 comment · Fixed by #60
Assignees
Milestone

Comments

@WesCossick
Copy link
Member

When you try to use a command that doesn't exist, the error is confusing, especially at the root level. See:

@WesCossick WesCossick added this to the 0.1.0 milestone Mar 8, 2019
@WesCossick WesCossick self-assigned this Mar 8, 2019
@WesCossick
Copy link
Member Author

WesCossick commented Mar 8, 2019

Instead, something like...

You provided "fake" to "node entry.js"
If you were trying to pass in data, this command does not accept data
If you were trying to use a command, did you mean [suggestion]?
For more assistance, see: node entry.js --help

...would be clearer. The suggestion would tie into #27, and should only appear if a close enough match exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant