Fixed column positions in test assertions to match actual parser output:
- Line 6: moved ^ to point at ID type instead of colon delimiter
- Line 98: moved ^ to point at IN keyword instead of name variable
Neovim's built-in filetype detection maps .hx to 'haxe', which
caused the test framework to attempt loading haxe.so instead of
helixql.so.
Changes:
- Renamed test file from test.hx to test.helixql
- Added vim modeline to ensure correct filetype detection
- Removed helixql filetype mapping (not needed and doesn't override
Neovim's built-in detection anyway)
Problem: `@type` currently captures function calls but fails to
capture CTE names.
Solution: Don't capture types in invocations. Add pattern for `cte`.
- Bash does not have boolean values and the builtin `true`
and `false` commands are already covered by another capture.
- The grammar has a `number` node and it's already captured.
Problem: Gitlab has too frequent outages, which break automation.
Solution: Drop all Gitlab-hosted parsers (two of which have been
unmaintained for years).
Problem: The commit fc37d05c36 broke parsing a textobjects query.
Solution: Downgrade parser to previous commit and pin it (until we can move it to tier 1).
Highlights the dollar symbol properly in multi-symbol contexts, like `$3.some.properties`.
There was already a fix for a similar issue on #8067, but it only addressed `$.some.properties`, but not the variant with the argument number in it.
* use uniform scope node instead of literal matching
This avoids the need to refactor if other scope types are added. Maybe
helps performance as well.
* add method expression highlight
Problem: These patterns were impossible, since children need to be children of
every subtype of a supertype to be captured in this way. As subtypes
could appear as children themselves, the query code silently "skipped
over" the supertype restriction in the pattern. This was fixed in
tree-sitter v0.26.0, which now (correctly) flags these patterns as
"impossible".
Solution: Add the appropriate child nodes explicitly.
Problem: These patterns were impossible, since children need to be children of
every subtype of a supertype to be captured in this way. As subtypes
could appear as children themselves, the query code silently "skipped
over" the supertype restriction in the pattern. This was fixed in
tree-sitter v0.26.0, which now (correctly) flags these patterns as
"impossible".
Solution: Add the appropriate child nodes explicitly.
The source of truth for formatting (according to make formatquery and
CI) is now ts_query_ls, so remove the no longer required script to
prevent divergence and bitrotting.
`trace32_hll_variable` has been removed from the grammar. The
queries are now capturing `symbol` instead. `symbol` is highlighted
as variable or constant.
This change does not break existing injections that currently ship with nvim-treesitter, but instead allows additional injections to be defined by users, like those found in the Max/MSP Jitter XML Shader format.
