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

Throwing / Handling Errors #18

Open
CortexPE opened this issue Aug 9, 2019 · 2 comments
Open

Throwing / Handling Errors #18

CortexPE opened this issue Aug 9, 2019 · 2 comments

Comments

@CortexPE
Copy link
Owner

CortexPE commented Aug 9, 2019

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.

@CortexPE
Copy link
Owner Author

CortexPE commented Aug 9, 2019

This is presently causing headache-inducing error messages for me 😠

@lukeeey
Copy link

lukeeey commented Aug 9, 2019

Still think its most important to get subcommands working correctly

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

No branches or pull requests

2 participants