aboutsummaryrefslogtreecommitdiffstats
path: root/tests/query/highlights/fusion
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: more `@keyword.type` capturesRiley Bruins2024-05-011-1/+1
|
* feat!: align standard captures with upstreamChristian Clason2024-01-192-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`
* chore(tests): consistent capturesChristian Clason2024-01-191-31/+31
|
* highlights: create subscoping for ternary operatorStephan Seitz2022-12-021-2/+2
| | | | | | | | | | After https://github.com/nvim-treesitter/nvim-treesitter/issues/470, we decided to use `@conditional` for ternary operator instead of operator despite `@conditional` is documented for keywords only. A sub-scoping can make it easier for people to highlight this operator group differently. Also unify the usage of `@conditional...` across languages.
* update fusion to version 1.1.1 (#2148)jirgn2021-12-233-1/+25
| | | | | | | | | | | | | | | | | | * feat(fusion): update tests * fix(fusion): update lockfile * fix(fusion): update to (highlight breaking) version 1.1.0 * update grammer to introduce afx support * update tests and queries * fix: revert lockfile update of unrelated grammars * fix: update to 1.1.1 and fix hightlights * fix: use @tag.attribute capture to match specs Co-authored-by: Jirgn <jirgn76@googlemail.com>
* feat(fusion): update testsJirgn2021-12-061-4/+4
|
* fix: incorrect hightlight groupsJirgn2021-11-261-1/+1
|
* fix: typo in highlight group punct(u)ationJirgn2021-11-262-10/+10
|
* feat: add fusion grammar and highlightsJirgn2021-11-262-0/+135