aboutsummaryrefslogtreecommitdiffstats
path: root/queries/css
Commit message (Collapse)AuthorAgeFilesLines
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-124-132/+0
|
* fix(css): do not fold top-level blocks (#7562)Michael Parque2025-02-191-0/+6
| | | | | | Using (block) makes the fold behavior only work on the line that the block starts not the start line of the statement, which is unideal when the preceding statement spans multiple lines. instead, use all top-level statements explicitly from https://github.com/tree-sitter/tree-sitter-css/blob/master/grammar.js
* feat(css): highlight `@keyframes` name (#7569)Omar Valdez2025-01-191-0/+2
|
* feat: import statement folds for common languagesRiley Bruins2024-05-011-1/+4
|
* feat(css): highlight square bracketsOmar Valdez2024-04-261-0/+2
|
* feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`Jaehwang Jung2024-03-161-1/+1
|
* chore: format queriesPhạm Huy Hoàng2024-01-211-2/+2
|
* fix(css): make the highlights more sensibleObserverOfTime2024-01-191-21/+27
|
* chore: query formattingPham Huy Hoang2024-01-194-65/+72
|
* feat!: align standard captures with upstreamChristian Clason2024-01-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`
* fix(css): tweak operator keyword highlightsRiley Bruins2023-11-221-1/+4
|
* refactor: Remove all `(ERROR) @error` capturesPham Huy Hoang2023-10-251-2/+0
| | | | | | | | | | | | As discussed in PR#5421, capturing `@error` is inconsistent, requiring deep nesting (or priority) in order to correctly have red backgrounds to it. Some queries has this capture, some don't. For consistency purposes, removing all of them is more preferable. For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)` to your custom queries.
* chore(injections)!: update injection syntax to 0.9Pham Huy Hoang2023-08-121-1/+2
| | | | | | | | | Since 0.9, @lang syntax is still available as fallback but will soon be deprecated. Because of that, new syntax should be adopted once 0.9 becomes the baseline requirements for nvim-treesitter - update health check - update doc
* perf: remove match where possibleAmaan Qureshi2023-04-211-2/+2
|
* 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
* highlights(css): use more specific groupsObserverOfTime2022-11-261-5/+6
|
* feat(spell): support more languagesLewis Russell2022-09-261-1/+1
|
* highlights(css): fix property highlightingStephan Seitz2022-09-101-1/+1
| | | | | | | | Apply fix as suggested by https://github.com/binhtran432k Fixes #3395 Co-authored-by: Trần Đức Bình <binhtran432k@users.noreply.github.com>
* Added fix for incorrect CSS indent after closing bracketDaniel Woznicki2022-03-191-3/+2
| | | | Added a failing test for possible broken CSS syntax tree
* Revert "Comment: use `@combined` to create just one tree per buffer (#1252)"Santos Gallegos2021-05-071-1/+1
| | | | This reverts commit 4a7a713c527f57c355bc817f16fc6d955b8cce9b.
* Comment: use `@combined` to create just one tree per buffer (#1252)Santos Gallegos2021-04-281-1/+1
| | | | | | | | | | | | * Comment: use `@combined` to create just one tree per buffer There is no need to create a tree per line/block for comments. Should fix https://github.com/nvim-treesitter/nvim-treesitter/issues/1251 * Add injections for scss * Fix jsonc * Combine jsdoc
* Fix invalid node type in CSS queriesStephan Seitz2021-03-161-1/+0
|
* Add comment parser to highlight comment tags (#893)Santos Gallegos2021-03-121-0/+1
| | | Closes #236
* feat: use @ignore for comments and multiline stringselianiva2021-03-011-0/+1
|
* feat: added more fold querieselianiva2021-01-041-0/+3
|
* css: add indent supportThanabodee Charoenpiriyakij2020-12-031-0/+9
|
* fix(queries): use vim-match for non lua regexesSteven Sojka2020-08-161-1/+1
|
* refactor: use newly introduced consolidated syntaxTravonteD2020-06-201-53/+72
|
* - #76 update the predicate syntax for ruby and cssTravonteD2020-06-111-2/+2
|
* Add css highlight queriesTravonteD2020-06-021-0/+72