-
Notifications
You must be signed in to change notification settings - Fork 659
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
Invalid query throws n.Term is not a constructor
#1871
Comments
What are you expecting from the query XXXX? |
I expected a different error message, like "Invalid Query" or "Invalid Token", but the error is not handled and it throws an internal error. |
@mathiasrw Can you assign this to me? Thanks! |
@vishal6557 Open Source project don't use assignment, especially for people that are outside the project. Where did you learn that project need to assign the task to you? |
@jcubic Thank you for your feedback! You're right—open-source projects flourish through collaboration and volunteer efforts. My goal was simply to offer help with this issue, aiming to contribute positively without overstepping. |
Fix released as part of v4.3.1 |
I've noticed that the error message on the invalid token looks like this:
When executing:
It looks like the invalid token is not handled and it just throws an unhandled exception.
You can see this on my Terminal App:
https://codepen.io/jcubic/pen/dVBaRm
The text was updated successfully, but these errors were encountered: