nvim-treesitter/queries/css, branch fix/lua

feat!: drop modules, general refactor and cleanup

2025-05-12T16:43:40Z

fix(css): do not fold top-level blocks (#7562)

2025-02-19T17:12:46Z

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)

2025-01-20T03:29:24Z

feat: import statement folds for common languages

2024-05-01T08:00:01Z

feat(css): highlight square brackets

2024-04-27T01:40:20Z

feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`

2024-03-16T12:51:16Z

chore: format queries

2024-01-21T14:55:02Z

fix(css): make the highlights more sensible

2024-01-19T15:58:37Z

chore: query formatting

2024-01-19T15:58:37Z

feat!: align standard captures with upstream

2024-01-19T15:58:37Z

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 highlights

2023-11-23T00:11:45Z

refactor: Remove all `(ERROR) @error` captures

2023-10-25T16:18:50Z

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.9

2023-08-12T15:34:15Z

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 possible

2023-04-21T22:24:17Z

use indent.X syntax for captures and properties of set directives

2023-03-24T17:07:53Z

update CONTRIBUTING.md adjust indents for bass fix doc capture comment

highlights(css): use more specific groups

2022-11-26T11:17:51Z

feat(spell): support more languages

2022-09-26T12:47:12Z

highlights(css): fix property highlighting

2022-09-10T20:02:07Z

Apply fix as suggested by https://github.com/binhtran432k Fixes #3395 Co-authored-by: Trần Đức Bình

Added fix for incorrect CSS indent after closing bracket

2022-03-19T11:29:36Z

Added a failing test for possible broken CSS syntax tree

Revert "Comment: use `@combined` to create just one tree per buffer (#1252)"

2021-05-07T14:51:57Z

This reverts commit 4a7a713c527f57c355bc817f16fc6d955b8cce9b.

Comment: use `@combined` to create just one tree per buffer (#1252)

2021-04-28T12:19:07Z

* 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 queries

2021-03-16T17:52:43Z

Add comment parser to highlight comment tags (#893)

2021-03-12T16:21:46Z

Closes #236

feat: use @ignore for comments and multiline strings

2021-03-01T22:28:53Z

feat: added more fold queries

2021-01-04T10:51:23Z

css: add indent support

2020-12-03T13:32:59Z

fix(queries): use vim-match for non lua regexes

2020-08-16T16:31:56Z

refactor: use newly introduced consolidated syntax

2020-06-20T13:03:39Z

- #76 update the predicate syntax for ruby and css

2020-06-11T14:38:19Z

Add css highlight queries

2020-06-02T19:11:35Z