Elm tree sitter
Why am I doing this?
I believe that Elm would greatly benefit from better tooling, the ultimate goal is to write a language server integration. This is a possible building block for that.
What it brings to the table:
- Very fast parsing, should enable parsing on each keystroke
- Resilient, even if you use wrong syntax, most of the file should still be recognized alright
- Should also be useful to the elm atom maintainers, as atom is using tree sitter as the new default for code highlighting (our ast might be too expressive). Highlight implementation still needs to be done if wanted.
What is this tested with?
This is tested against the tests included in the repo and:
So it should work fine for a fair amount of code. What's not tested right now is behavior in error cases.
Want to help?
Help writing some tests or simply find valid elm files, that fail parsing.
Test are located in the
test folder and separated in parser tests and highlighting tests.