On 11/11/2023 17:43, Loïc Lemaître wrote:
Thanks for the patch ! It fixes the bug.
But unfortunatly, there is another similar bug in
/treesit-forward-sexp/, that you can reproduce with that example:
({(<A></A>)});
The problem in this case is that the code doesn't parse (one of the
nodes in the parse tree is ERROR). Removing either the curlies, or the
outer parens pair makes the code valid and the behavior
correspondingly better.
Although for treesit-forward-sexp to jump between curlies in
{(<A></A>)};
we'll also need to add "statement_block" to js--treesit-sexp-nodes.