Error reporting for attribute value without closing "

[FreHu]

Unbalanced quotes are probably a common occurrence when writing xml and the errors about a missing EQUALS here are not clear at all. Maybe this situation could be reported more intelligently?

The errors are not the same if I leave an unclosed attribute before another empty attribute:

[bd82]

It may be possible to improve the parser by:
defining in the lexer an "unclosed quotes token", e.g when encountering a line terminator when lexing quoted string.

[bd82]

Perhaps it would be possible to also identify mismatched closing quotes.

[bd82]

The relevant feature in Chevrotain that could be used to implement this is:

• https://chevrotain.io/docs/features/custom_token_patterns.html

[FreHu]

Another related issue: if there is a missing attribute, the problematic xml element is underlined. This is too much - if you are missing an attribute on the root element, your entire file becomes a squiggle.

Since there is no attribute to underline, could only the opening element name be underlined in this case?

[bd82]

I don't think the underlining is aware of the XML structure, it just displays errors as outputted by the parser.
Perhaps the question is how the parser outputs the errors, and maybe if we can modify its error recovery logic.

Can you post a small sample XML that reproduces this issue?

[FreHu]

giant squiggle turned out to be my mistake