We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Parse errors shouldn't be directly sent from the parser, throw only one at a time.
Throwing several errors at once might cause confusion because not only will it be inconsistent and unpredictable, the user might even be spammed.
The text was updated successfully, but these errors were encountered:
This is presently causing headache-inducing error messages for me 😠
Sorry, something went wrong.
Still think its most important to get subcommands working correctly
No branches or pull requests
Parse errors shouldn't be directly sent from the parser, throw only one at a time.
Throwing several errors at once might cause confusion because not only will it be inconsistent and unpredictable, the user might even be spammed.
The text was updated successfully, but these errors were encountered: