Jonatan Kłosko

Hmm, the module attributes look off, and some of the keywords like `def`, `case` are not highlighted properly. You can play around with queries order, I think the built-in highlighter...

Sounds good, please go ahead! I've just signed into crates, so feel free to add me :)

Regarding code organisation, on one hand it seems like a tree-sitter convention to keep all grammars as separate repositories, but separating heex/surface feels quite scattered. I saw that in [tree-sitter-typescript](https://github.com/tree-sitter/tree-sitter-typescript) ...

To support code navigation for `` I think we would parse `Mod.fun` into a single node and then use injections to parse it as Elixir code, which would be a...

> Alright, so it is either three directories in this repo or three separate repositories. Both are fine by me. It depends on how many colocated changes we will have...

Ideally we would move to the tree-sitter org yeah, otherwise the `elixir-editors` sounds good to me (just so we don't have `elixir-tree-sitter/tree-sitter-elixir` ^^).

> I think tag definitions are what drive the code navigation capability? I think so, although code navigation is not supported for Rust at this point. I think the Rust...

@connorlay as for HEEx the only thing that I'm unsure about is how to parse ``, if we want to use injection we need to parse "tag" into it's own...

We decided to focus on alternative sharing variants, as outlined in https://github.com/livebook-dev/livebook/issues/1153#issuecomment-1405625519. We may revisit this in the future, though after further consideration sharing regular session with less permissions doesn't...

@nallwhy thanks for the effort! I've just implemented the approach described above in #1622 :)