| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Problem: Gitlab has too frequent outages, which break automation.
Solution: Drop all Gitlab-hosted parsers (two of which have been
unmaintained for years).
|
| |
|
|
|
| |
Breaking change: removed double parenthesis as valid opening to
arithmetic expansion. (Only `$((` is allowed according to the manual.)
|
| |
|
|
|
| |
`trace32_hll_variable` has been removed from the grammar. The
queries are now capturing `symbol` instead. `symbol` is highlighted
as variable or constant.
|
| |
|
|
|
| |
Co-authored-by: Christian Clason <c.clason@uni-graz.at>
Co-authored-by: Riley Bruins <ribru17@hotmail.com>
Co-authored-by: Tayfun Bocek <tayfunbocek@live.ca>
|
| |
|
| |
Switch parser to https://github.com/airblast-dev/tree-sitter-gdshader
|
| |
|
| |
Co-authored-by: Riley Bruins <ribru17@hotmail.com>
|
| | |
|
| |
|
|
| |
This reverts commit 8c8742871a1489afd7878bfee4bc40465f4a116a.
|
| |
|
|
| |
https://github.com/cathaysia/tree-sitter-jinja/issues/37
|
| |
|
|
|
|
|
|
|
|
|
| |
The majority of jinja variables aren't assigned any highlights at all.
Assign @variable to all identifiers.
Jinja filters without parameters are not highlighted as functions: add a
query for these.
Refine the existing @variable.member to only capture identifiers instead
of broader nodes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Not easy to run all checks and tests locally. Redundant CI
workflows.
Solution: Separate CI into two workflows:
* lint: Lua files (stylua, luals), query files (valid captures,
predicates, directives using tsqueryls), docs
(SUPPORTED_LANGUAGES.md) -- does not need parser installation
* tests: parsers (ABI compatibility), query files (tsqueryls on
Linux/macOS; nvim on Windows), highlight and indent tests (separated
for better readability) -- needs parser installation (but only once)
Switch to https://github.com/nvim-treesitter/highlight-assertions fork
with ABI 15 support.
Run all tests (on Linux and macOS) through `make` (`formatlua`,
`checklua`, `lintquery`, `formatquery`, `checkquery`, `docs`, `tests`),
which downloads and caches all necessary dependencies.
Remove `update-readme` workflow (replaced by lint job on PRs).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Problem: Tracking parser revision in lockfile and allowing override
through the parsers module complicates the code. In addition, only
revision changes are handled robustly, not changes to other installation
info.
Solution: Track parser revision in the parsers module directly. Reload
parser table on every install or update call. Support modifying parser
table in a `User TSUpdate` autocommand.
|
| |
|
|
|
| |
- Apply suggestions from Lewis to only parse visible lines
- Fix failed tests
|
| | |
|
| |
|
|
|
|
| |
(+ add Check to mkDerivation bash matches)
(+ add Check to mkDerivation bash matches)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix(python): don't highlight attribute name as builtin
* fix(python): highlight `@variable.member` correctly for member access context
* test: add test
* test: expand test
* docs: update comment
* refactor: change order, remove priority override
* style: remove extra newline
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Prometheus, label values are treated as strings when used with the
`=` and `!=` operators, and as regular expressions when used with the
`=~` and `!~` operators.
Injecting and then highlighting all label values as regex leads to a
situation where entirely valid **string** label values containing regex
special characters are mistakenly parsed and highlighted as regex. This
results in syntax errors, causing labels to be highlighted incorrectly.
For example, in `foo{bar=~"[a-z]{1,3}"}`, `{` and `}` are regex special
characters, so regex highlighting is expected. However, in
`foo{path="/foo/{id}"}`, `{` and `}` are just part of the string and
have no special meaning, so the whole value should be highlighted as a
string.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This patch captures `::` as `@operator` within
`(unary_typed_expression)` and `(typed_expression)`. These should be the
only two cases that the parser can emit when encountering `::` in the
source, but as a fallback it is still captured as `@punctuation` in all
other cases.
The reasons for capturing `::` as an operator are i) the close relation
with the other type-operators `<:` and `>:` and ii) the fact that it is
treated as an operator by the Julia parser, just like `<:` and `>:`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
...as well as some fold and injection queries.
|
| |
|
|
|
|
|
|
|
| |
* chore(php): update maintainers
* feat(php): update php rules, highlight imported functions/consts
* feat(php): indent inside property hooks
* chore: update php and php_only revision
|
| |
|
|
|
|
| |
I think these have been broken since the query parser update. Basically
the inner node for the string content was preventing injections because
include-children was not set.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This reverts commit f08a9d97f7a2ac02115a5c1c8e3973b2634d996b.
(Fixed by skipping bindings when generating.)
|
| |
|
|
| |
Adds support for new node type `elif_block`.
|
