Amaan Qureshi

setting `_expression` (well now `_expression_not_binary` as that's the one w/ conflicts) to have a dynamic precedence of -1 fixes this, but causes issues elsewhere. maybe removing identifiers from the expressions...

the first case should be fixed, I'll agree. About binary expressions - that's just asking for a mess of conflicts. So, would just fixing the first case be good enough?

This increases state count too much, I believe this can be refactored and improved

Don't use Neovim from snap, it always has issues like this, use HEAD or your distro's package manager (or the app image)

Just FYI, this won't be solved here - you could create a grammar for thymeleaf to then be injected here

No, the HTML grammar does not look for them. The way it works is an injections query is created to *inject* languages into certain nodes of the HTML grammar -...

docker issue w/ upstream, same issue in typescript/xml, I'll close as a dupe of the upstream https://github.com/tree-sitter/tree-sitter/issues/3233

Tracking brackets/parenthesis in the delimiter stack sounds a bit complex, but it might also solve this case ```py def foo(a): return (a. bar) ``` PR welcome :)

this one would be really *really* hard to fix w/o a mechanism to *disallow* rules in certain contexts (objects in expression statements in if statements)

So most statements cannot have an object literal? Interesting