`NodeType.isError` for a large and valid JSON document

From the support I received in Check JSON syntax using language pack - #5 by transform, I use the following to validate a JSON document.

const tree: Tree = syntaxTree(this.cm.state);
if (tree) {
  const cursor: TreeCursor = tree.cursor();
  while (cursor.next()) {
    const sn: SyntaxNode = cursor.node;
    const nt: NodeType = sn.type;
    if (nt.isError) {
      // Invalid JSON document.
// Valid JSON document.

When copy/pasting valid but large JSON document, around 350 (23,384 characters) lines long, the code above detects an invalid JSON document. NodeType.isError is true.

However, just placing the cursor at the end of the JSON document and inserting a space character, causes the code above to re-run and validation passes.

This problem does not occur with smaller JSON documents.

I have the SyntaxNode and NodeType but because they contain circular references I can’t just JSON.stringify them into this post.

  1. Is this a known issue?
  2. What can I do to debut this further?

Oh, that’s a good point. The parser will delay parsing when it takes too long, and insert error nodes at the end of any constructs that were unfinished at the point where it stopped. You may need to add a rule that when the tree doesn’t span the entire document, you ignore error nodes near its end.

Thanks @marijn

  1. I can see how that would prevent falsely reporting an error, but how should a large JSON document be checked for correctness if error nodes must be ignored?
  2. How can I check whether a tree spans the entire document?

Compare syntaxTree(state).length to state.doc.length. You only need to ignore the errors near the end of the document.