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

Ability to distinguish between an erroring command and a command with an invalid parameter match. #58

Closed
amthorn opened this issue May 26, 2021 · 0 comments · Fixed by #59
Assignees
Labels
enhancement New feature or request

Comments

@amthorn
Copy link
Owner

amthorn commented May 26, 2021

Is your feature request related to a problem? Please describe.
It's not very helpful when commands that error only tell me that the command is invalid. It would be nice to have an error message that can tell me if the command is simply invalid or if the parameter itself is not found. Additionally, it would be nice to see what the closest command match is.

Describe the solution you'd like
A clear and concise description of what you want to happen.
When a command is not found, tell me why? Is it because of the command syntax isn't valid? Or because the parameter itself is bad.

Describe alternatives you've considered
N/A

Additional context
N/A

@amthorn amthorn added the enhancement New feature or request label May 26, 2021
@amthorn amthorn self-assigned this May 26, 2021
amthorn added a commit that referenced this issue May 26, 2021
* Added a best match in event of an error

* 100% coverage

* Keep at verbose
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant