aboutsummaryrefslogtreecommitdiffstats
path: root/tests/query/highlights
Commit message (Collapse)AuthorAgeFilesLines
* feat(parsers)!: remove gitlab-hosted blueprint, fusion, jsoncChristian Clason2025-12-063-159/+0
| | | | | | | Problem: Gitlab has too frequent outages, which break automation. Solution: Drop all Gitlab-hosted parsers (two of which have been unmaintained for years).
* feat(bash): update parserChristian Clason2025-12-061-4/+4
| | | | | Breaking change: removed double parenthesis as valid opening to arithmetic expansion. (Only `$((` is allowed according to the manual.)
* feat(t32)!: update parser and queries (#8276)Christoph Sax2025-11-123-7/+7
| | | | | `trace32_hll_variable` has been removed from the grammar. The queries are now capturing `symbol` instead. `symbol` is highlighted as variable or constant.
* feat(parsers): add zsh support (#8240)George Harker2025-11-051-0/+358
| | | | | 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>
* feat!(gdshader): replace gdshader parser and queries (#8244)Tayfun Bocek2025-10-301-0/+26
| | | Switch parser to https://github.com/airblast-dev/tree-sitter-gdshader
* fix(python): regex injection not working for concatenated strings (#8197)Lev Velykoivanenko2025-10-262-0/+30
| | | Co-authored-by: Riley Bruins <ribru17@hotmail.com>
* feat(proto): more delimiter, property highlightsRiley Bruins2025-08-311-0/+62
|
* Revert "fix(jinja): remove crashing pattern"Robert Muir2025-08-051-0/+19
| | | | This reverts commit 8c8742871a1489afd7878bfee4bc40465f4a116a.
* fix(jinja): remove crashing patternChristian Clason2025-07-211-19/+0
| | | | https://github.com/cathaysia/tree-sitter-jinja/issues/37
* fix(jinja): assign highlights to all variables and functionsRobert Muir2025-07-193-0/+53
| | | | | | | | | | | 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.
* tests(gleam): fix assert tests that no longer parse correctlyChristian Clason2025-05-121-5/+5
|
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-121-2/+2
|
* fix(python): highlight all types of docstrings (#7788)Jakob Zahn2025-04-031-0/+121
|
* fix(python): prioritize builtin functionsdcho2025-03-211-0/+3
|
* fix(python): don't highlight parameter name as builtin (#7732)Salomon Popp2025-03-132-4/+16
|
* fix(python): highlight function calls correctly (#7728)Salomon Popp2025-03-122-0/+35
|
* fix(python): don't highlight attribute name as builtin (#7712)Salomon Popp2025-03-111-0/+5
| | | | | | | | | | | | | | | * 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
* feat(php): add support for new relative_name nodeCaleb White2025-02-262-27/+147
|
* feat(promql): do not use regex for string labels (#7669)Daniil Leontev2025-02-202-0/+43
| | | | | | | | | | | | | | | | | 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.
* fix(php): properly highlight grouped imported functions and constantsCaleb White2025-01-021-0/+12
|
* fix(julia): treat :: as operator in type contextsFredrik Ekre2024-11-231-3/+3
| | | | | | | | | | | | 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 `>:`.
* feat(http): more comprehensive highlightsRiley Bruins2024-11-221-0/+33
|
* feat(python): highlight modulesOmar Valdez2024-11-211-1/+1
|
* fix(rust): highlight parameters with ref in definitionRiley Bruins2024-11-031-0/+8
|
* feat(gleam,luau): use `@keyword.type` captures (#7181)Riley Bruins2024-09-261-3/+3
|
* feat(wing): add many missing highlightsRiley Bruins2024-09-021-2/+4
| | | | ...as well as some fold and injection queries.
* feat(php): php 8.4 support (#6741)Caleb White2024-08-181-0/+35
| | | | | | | | | * 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
* fix(r): resolve highlight regressionsRiley Bruins2024-06-291-3/+4
|
* feat(r)!: update parser and queriesChristian Clason2024-06-271-5/+4
|
* fix(gleam): remove incorrect builtin highlight (#6757)Louis Pilfold2024-06-172-10/+10
|
* feat(php): add highlights for scoped_property_accessCaleb White2024-05-141-0/+3
|
* fix(haskell): update queries and tests for rewritten parser (#6580)Marc Jakobi2024-05-071-9/+20
|
* feat: more `@keyword.type` capturesRiley Bruins2024-05-019-18/+18
|
* fix(php): parameter and operator touch-upsRiley Bruins2024-04-252-2/+2
|
* fix(wing): update to new repo (#6446)Mark McCulloh2024-04-141-1/+1
|
* fix(julia): adapt queries to grammar changes (#6429)Sergio A. Vargas2024-04-141-1/+1
|
* Revert "ci(tests): drop flaky wing parser tests"Christian Clason2024-04-142-0/+23
| | | | | | This reverts commit f08a9d97f7a2ac02115a5c1c8e3973b2634d996b. (Fixed by skipping bindings when generating.)
* feat(t32): update queries from upstream (#6440)Christoph Sax2024-04-141-1/+3
| | | | Adds support for new node type `elif_block`.
* ci(tests): drop flaky wing parser testsChristian Clason2024-04-132-23/+0
|
* feat(nix): misc cleanups + comment injection (#6418)Riley Bruins2024-04-091-0/+5
| | | | | | | | | * fix(nix): highlight strings within interpolations * feat(nix): move `derivation` to function.builtin * fix(nix): removes all `priority` workarounds * feat(nix): arbitrary injections using `#` comments
* chore(php): trim down testsCaleb White2024-03-274-153/+3
|
* fix(php): fix use_{as,instead_of}_clause highlightsCaleb White2024-03-271-3/+14
|
* feat(php): add highlight testsCaleb White2024-03-274-0/+250
|
* Update Clojure highlights to be metadata aware (#6213)Noah2024-03-191-4/+66
|
* feat(highlights)!: `@keyword.storage` → `@keyword.modifier`Jaehwang Jung2024-03-161-2/+2
|
* feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`Jaehwang Jung2024-03-167-18/+18
|
* feat(highlights)!: enforce documented captures (#6232)Christian Clason2024-03-031-2/+2
| | | | | | | | | | | | | | | Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin.
* feat(latex): pre-compiled header highlights, testsRiley Bruins2024-02-061-0/+33
| | | | | Also moves comment highlights to the very end to make them more future-proof.
* fix(highlights): improve member/property distinctionObserverOfTime2024-01-195-18/+18
|
* feat!: align standard captures with upstreamChristian Clason2024-01-1945-256/+256
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Sharing highlight queries with upstream tree-sitter and Helix is difficult. Solution: Where reasonable, use capture names in tree-sitter's standard list or Helix's Atom-style hierarchy. Specifically: * tree-sitter "standard capture names" (https://github.com/tree-sitter/tree-sitter/blob/3f44b896852eb7daaa6df4fb778c9bb52c70c815/highlight/src/lib.rs#L20-L72): - `@parameter` -> `@variable.parameter` - `@field` -> `@variable.member` - `@namespace` -> `@module` - `@float` -> `@number.float` - `@symbol` -> `@string.special.symbol` - `@string.regex` -> `@string.regexp` - `@text.*` -> `@markup.*` (`strong`, `italic`, `link`, `strikethrough`; with exceptions; see below) - `@text.title` -> `@markup.heading` - `@text.literal` -> `@markup.raw` - `@text.reference` -> `@markup.link` - `@text.uri` -> `@markup.link.url` (in markup links) - `@string.special` -> `@markup.link.label` (non-url links) - `@punctuation.special` -> `@markup.list` (markdown lists only; move subitems from `@text.todo`) * Helix captures (https://docs.helix-editor.com/master/themes.html#syntax-highlighting): - `@method` -> `@function.method` - `@method.call` -> `@function.method.call` - `@text.{todo,warning,note,danger}` -> `@comment.{error,warning,hint,info,todo}` - `@text.diff.{add,delete,}` -> `@diff.{plus,minus,delta}` - `@text.uri` -> `@string.special.url` (outside markup) - `@preproc` -> `@keyword.directive` - `@define` -> `@keyword.directive`(`.define`?) - `@storageclass` -> `@keyword.storage` - `@conditional` -> `@keyword.conditional` - `@debug` -> `@keyword.debug` - `@exception` -> `@keyword.exception` - `@include` -> `@keyword.import` - `@repeat` -> `@keyword.repeat` * cleanup - remove some redundant `@conceal` (but still allow it for conceal-only patterns) - remove obsolete `@error` (syntax linting is out of scope for this repo) - sort, cleanup capture list in `CONTRIBUTING.md`