Skip to content

elm-tooling/tree-sitter-elm

Folders and files

NameName
Last commit message
Last commit date

Latest commit

3b373a3 · Mar 30, 2025
Mar 30, 2025
Apr 10, 2019
Mar 30, 2025
Mar 30, 2025
Jul 25, 2021
Jul 31, 2021
Aug 21, 2022
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Apr 7, 2022
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Nov 22, 2020
Mar 30, 2025
Mar 30, 2025
Apr 13, 2021
Mar 30, 2025
Mar 30, 2025
Dec 18, 2023
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Mar 30, 2025
Sep 4, 2020

Repository files navigation

Build Status

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.

Thanks

Very very big thanks goes out to @klazuka and the people of intellij-elm as I basically stole how they're creating their parser minus the GLSL implementation.

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.