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

Error messages remaining between playground runs #269

Open
MullinsN opened this issue Feb 23, 2021 · 0 comments
Open

Error messages remaining between playground runs #269

MullinsN opened this issue Feb 23, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@MullinsN
Copy link

MullinsN commented Feb 23, 2021

Question

Does it make sense to keep error messages at the bottom of the screen when the next playground is run?

The error messages, seem to hang around for a bit and then disappear, however I have noticed sometimes some error messages just remain at the bottom of the panel. Are they getting orphaned from the timed process that clears them down.

Additional context

Personally I would prefer to have the error message (s) cleared down between runs, as soon as I press the run button?

Also I don't know if it is possible, but if the parser knows where it thinks the error is, can it not jump to the line and column in the playground as well as displaying the error message, with a cursor colour change?

The error text we receive, how often does the whole message provide value?

Unexpected token (22:13) 20 | }, 21 | { > 22 | "$group" { | ^ 23 | "_id": { 24 | "year": "$year", 25 | "genre": "$genres"

Lets be honest, the Unexpected token (22:13) is the key in that message, if the rest of message has value, then put it on the next line, so the V needs to be pressed.

I suppose in a round about way I am saying, can the error messages be improved / structured in a more meaningful way.

@alenakhineika alenakhineika added the enhancement New feature or request label Mar 15, 2021
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

No branches or pull requests

2 participants