There is a bug with current "customif-statment" grammar.js implementation whereby, the custom directive can not start with the letter "e". for example @exxx code @endxxx will not work. See the commit relating to #3
What happens when including "e"
The parser will be unable to pick up nesting correctly, using custom if_statements
The Reason behind the bug:
Simply because assertions such as lookahead and lookbehind are not supported in the RegEx when writing grammars in tree-sitter.
Fix:
This can possibly get fixed using external scanners, if someone proficient in C is happy to help. 🙃
There is a bug with current "custom
if-statment" grammar.js implementation whereby, thecustom directivecan not start with the letter "e". for example@exxx code @endxxxwill not work. See the commit relating to #3What happens when including "e"
The parser will be unable to pick up nesting correctly, using custom if_statements
The Reason behind the bug:
Simply because assertions such as lookahead and lookbehind are not supported in the RegEx when writing grammars in tree-sitter.
Fix:
This can possibly get fixed using external scanners, if someone proficient in C is happy to help. 🙃