aboutsummaryrefslogtreecommitdiffstats
path: root/queries/slint
Commit message (Collapse)AuthorAgeFilesLines
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-125-419/+0
|
* feat(slint): highlight enum members as constantsRiley Bruins2024-05-141-0/+3
|
* feat: standardize and document export keywordsRiley Bruins2024-05-131-1/+1
| | | | | | Many export keywords are captured as `@keyword.import`. This commit makes it so they are all captured like that, and mentions it in the documentation.
* feat: more `@keyword.type` capturesRiley Bruins2024-05-011-2/+2
|
* refactor(format): drop extra indentation for fieldPhạm Huy Hoàng2024-03-211-3/+2
|
* feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`Jaehwang Jung2024-03-161-3/+3
|
* feat(highlights)!: enforce documented captures (#6232)Christian Clason2024-03-031-1/+1
| | | | | | | | | | | | | | | 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(slint)!: change to the official parser (#6027)Tobias Hunger2024-02-095-132/+358
| | | | | | | | | | | This change replaces the slint parser written and maintained by @jrmoulton with the official one hosted in the slint-ui organization on github. A huge thank you to @jrmoulton for all his work on the tree-sitter parser! --------- Co-authored-by: jrmoulton <jaredmoulton3@gmail.com>
* chore: query formattingPham Huy Hoang2024-01-192-103/+126
|
* feat!: align standard captures with upstreamChristian Clason2024-01-191-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`
* feat: @spell on commentsJaehwang Jung2023-09-121-1/+1
|
* use indent.X syntax for captures and properties of set directivesGeorge Harker2023-03-241-4/+4
| | | | | | | | update CONTRIBUTING.md adjust indents for bass fix doc capture comment
* Update slint indent queriesChristian Clason2022-12-272-11/+12
|
* Update slint highlight queries for rewriteJared Moulton2022-12-271-42/+50
|
* highlights: create subscoping for ternary operatorStephan Seitz2022-12-021-1/+1
| | | | | | | | | | 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.
* feat(slint): <=> operatorShootingStarDragons2022-09-261-0/+1
| | | | | | | | Slint have support <=> operator, so add this for highlight, Next time when lockfile.json is update, then merge this one Log: slint
* highlights(slint): highlight operators and more punctuationStephan Seitz2022-05-211-0/+30
|
* Add slint parser configuration and queries (#2598)Jared Moulton2022-03-072-0/+128
* Add slint parser * Mark slint as experimental * Remove filetype and add slint to the lockfile * Update queries * Update varibable.builtin's and repeats * Update slint true false * Change export back to keyword * Change export back to include :)