Skip to content

Error messages remaining between playground runs #269

Open
@MullinsN

Description

@MullinsN

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions