I've developd a valid parser for a subset of a specific language and integrated it into a fork of this repo. The extension installs and works correctly, with the appopriate coloring being applied to the correct tokens. All document events (activation, change, etc.) fire at the appropriate times, but documents that contains MISSING and ERROR nodes in their CSTs do not produce the expected orange or red squiggly underline in vscode. It does not appear to be a theming issue. There is no reference to either of these in any code within the extension. I have to assume that the underlining is an automated response to a specific node encounter by vscode. If so, why to the error nodes from tree-sitter CSTs not trigger the expected behavior?
I've developd a valid parser for a subset of a specific language and integrated it into a fork of this repo. The extension installs and works correctly, with the appopriate coloring being applied to the correct tokens. All document events (activation, change, etc.) fire at the appropriate times, but documents that contains MISSING and ERROR nodes in their CSTs do not produce the expected orange or red squiggly underline in vscode. It does not appear to be a theming issue. There is no reference to either of these in any code within the extension. I have to assume that the underlining is an automated response to a specific node encounter by vscode. If so, why to the error nodes from tree-sitter CSTs not trigger the expected behavior?
Thanks!