tree-sitter-haxe
tree-sitter-haxe copied to clipboard
vantreeseba
Hi! Maybe I'm doing something wrong here. Just cloned the latest version of `tree-sitter-haxe` (93c3ce595e41727670f7c0e6c88afe16b5384f0d). `cd` into the cloned directory and ran `tree-sitter generate` (`tree-sitter` version 0.22.2). It fails with...
Using this page https://meimporta.eu/tree-sitter/json2ebnf.html we can get a navigable railroad diagram for tree-sitter grammars like this project. See also https://github.com/tree-sitter/tree-sitter/issues/2268 . Cheers !
This is more of a project request than a feature request, but it would be nice to have support for HXML ([Example implementation](https://github.com/vshaxe/haxe-TmLanguage#hxml-example)) 
Haxe 4 introduced inline xml aka "not-xml" syntax: ```haxe var a = children; var a = bar; // Self-closing tags var a = ; // Code interpolation, not exactly standard...
This was broken previously: ```haxe var x:T R>; ``` As a side effect of the change, builtin types used as type parameters also highlight properly now: ```haxe var i:Null; ```...
Package names are now highlighted with `@module`, and type names are highlighted with `@type`. This also removes the need for nested highlighting queries for package and import statements, so longer...
If it is a property access identifier, it will be treated as a keyword, otherwise as a literal.
Editors may not want to mark all of them with `@keyword`, for example [neovim](https://neovim.io/doc/user/treesitter.html#_treesitter-syntax-highlighting) provides more specific groups such as `@keyword.modifier` etc. so it is better to let the highlights.scm...