nvim-treesitter/queries/gdscript/highlights.scm, branch main

feat!: drop modules, general refactor and cleanup

2025-05-12T16:43:40Z

feat(gdscript): add new export annotations

2024-11-18T07:26:49Z

fix(formatter): simplify code, remove odd line break

2024-10-26T08:07:30Z

feat(highlights): capture wildcard patterns as `@character.special` (#7153)

2024-09-20T06:15:01Z

feat: standardize and document export keywords

2024-05-13T07:16:31Z

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` captures

2024-05-01T07:59:50Z

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

2024-03-16T12:51:16Z

feat(gdscript): update parsers and queries. (#6176)

2024-02-24T17:21:19Z

* feat(gdscript): add highlight for (pattern_guard "when") * feat(gdscript): update (type) highlights and support typed array * feat(gdscript): add highlight to attribute subscript ident * feat(gdscript): only apply @ constructor to init ident * feat(gdscript): replace greedy (parameters) match with independent match * feat(gdscript): add (typed_default_parameter) highlight * feat(gdscript): add (constructor_definition) indent * feat(gdscript): update big wall of built-in identifiers

feat(format-scripts): linewrap predicates

2024-02-23T08:42:01Z

"format-ignore".kick()

fix(format): handle list with 300 nodes

2024-01-30T15:59:27Z

Fixup format (#5934)

2024-01-20T09:47:56Z

* fix(format): newline between top-level field defs * fixup: newline between node and comment * fixup: optimize pattern

chore: query formatting

2024-01-19T15:58:37Z

refactor: manual pre-cleanup

2024-01-19T15:58:37Z

Moving comments, adding `format-ignore` to lines that will be better with it

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`

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.

docs: fix typos

2023-03-29T22:28:56Z

feat!: add `@keyword.coroutine` capture

2023-03-03T15:07:52Z

Update gdscript queries (#4405)

2023-03-02T07:28:13Z

* locals(gdscript): update locals * folds(gdscript): add folds * indents(gdscript): update indents with notes * highlights(gdscript): update highlights * docs(gdscript): add gdscript maintainer * indents(gdscript): add ERROR auto indent Co-authored-by: Amaan Qureshi * highlights(gdscript): use text.uri for get_node and node_path * highlights(gdscript): add "@" of annotation as attribute * highlights(gdscript): use keyword.operator for "new", match all attribute_call * highlights(gdscript): update (underscore) and (pattern_open_ending) --------- Co-authored-by: Amaan Qureshi

highlights(gdscript): use more specific groups

2022-11-26T11:17:51Z

Prefer lua-match over match

2021-11-23T09:02:06Z

as string.find is much quicker than vim.regex:match*

Remove regex for field

2021-07-21T22:03:48Z

feat(keywords) merge return and yield into keyword.return group

2021-07-04T19:49:17Z

feat(keywords) add keyword.return & keyword.yield

2021-07-04T19:49:17Z

Fix identifier type check

2021-04-18T18:40:58Z

Fix GDScript highlighting

2021-04-18T18:40:58Z

add gdscript

2020-12-31T13:27:43Z