nvim-treesitter/queries/yaml, branch master

More bash injection support for Taskfile (#7805)

2025-04-07T19:08:22Z

feat(yaml): inject bash for taskfiles (#7804)

2025-04-06T17:09:27Z

feat(yaml): capture "boolean strings" (#7512)

2025-02-19T17:37:18Z

See for example: https://www.bram.us/2022/01/11/yaml-the-norway-problem/ values based on: https://yamllint.readthedocs.io/en/stable/rules.html#module-yamllint.rules.truthy Parser targets YAML 1.2, which has stricter promotions.

refactor(queries): Remove quotes from properties in set! directive

2024-07-28T09:43:41Z

refactor(format): drop extra indentation for field

2024-03-21T14:51:26Z

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

fix(highlights): improve member/property distinction

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`

feat(locals)!: switch to upstream captures

2024-01-19T15:58:37Z

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.

fix(yaml): promql injections block

2023-09-15T10:53:44Z

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

fix(yaml): typo in promql injection (#5130)

2023-07-19T16:41:50Z

feat(promql,yaml): add parser and yaml injections

2023-07-18T07:03:11Z

Signed-off-by: Michael Hoffmann

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

injections(yaml): fix injections

2022-12-21T22:38:07Z

folds(yaml): Fold at the entire node, not at the body.

2022-10-16T23:06:09Z

highlights: use @preproc where appropriate

2022-10-15T15:49:01Z

feat(spell): support more languages

2022-09-26T12:47:12Z

fix(indents/yaml): only indent mapping pair if value is a block

2022-06-14T20:37:52Z

This improves the following situation, in which '|' is the cursor position: ```yaml - key1: value1 key2: value2| ``` Before this commit, by pressing Enter would result in this indentation: ```yaml - key1: value1 key2: value2 | ``` Which is less convenient than this: ```yaml - key1: value1 key2: value2 | ```

fix(indents/yaml): improve error handling

2022-06-14T20:37:52Z

This helps to solve the first issue reported at #1377. The problem is that the line loses its indentation when we start inserting a new mapping pair (specifically, when we enter the character ":"). The issue seems to be solved by auto indenting ERROR nodes.

fix(indents/yaml): indent sequence/list items

2022-06-14T20:37:52Z

This solves the second issue reported at #1377, in which the cursor would not be aligned with the line "key2: value2" when entering a new line below it. ```yaml - key1: value1 key2: value2 ```

injections(yaml): inject at command list for Gitlab script

2022-02-05T17:25:35Z

injections(yaml): injection on Gitlab's before_script/after_script

2022-02-05T17:25:35Z

yaml(injections): Also add heuristics for Gitlab CI bash

2021-11-28T14:01:34Z

injections(yaml): inject bash on key "run"

2021-11-28T14:01:34Z

yaml: improve highlights and locals (#946)

2021-10-27T03:47:59Z

- More scopes - Highlight strings as strings - Recognize more keys/fields Improvements can be seen with this weird yaml: ```yaml { foo: bar } --- {a: [b, c], [d, e]: f} --- - { single line, a: b} - { multi line, a: b} --- "fooo": bar 'foo': bar one: two ```

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

YAML: update queries (#1203)

2021-04-18T21:51:03Z

Closes https://github.com/nvim-treesitter/nvim-treesitter-refactor/issues/18

Yaml: update locals (#1172)

2021-04-10T00:36:19Z

The parser doesn't break the symbols in `*` `&` from the name of anchors/aliases. So go to definition doesn't work, but highlight of usage does :D Test with ```yaml Defaults: &defaults Company: foo Item: 123 Computer: <<: *defaults <<: *defaults Price: 3000 ``` Ref https://github.com/nvim-treesitter/nvim-treesitter-refactor/issues/18

Add comment parser to highlight comment tags (#893)

2021-03-12T16:21:46Z

Closes #236

YAML: add locals

2021-02-10T21:25:12Z

This is so incremental selection works

Yaml: fix folds

2021-02-07T14:37:21Z

Fix https://github.com/nvim-treesitter/nvim-treesitter/issues/887 (block_node) includes more nodes to fold, test with: ```yaml days: Monday: - test: example Tuesday: - test: example Wednesday: - test: example - test: example Thursday: - test: example Friday: - test: example - foo: | One Two Three ```

feat: added more indent queries

2021-01-14T13:43:04Z

feat: added more fold queries

2021-01-04T10:51:23Z

wildcards to capture keys

2020-12-25T14:56:49Z

simplify treatement of escape sequences

2020-12-25T14:56:49Z

remove plus from list of punctuation

2020-12-25T14:56:49Z

first draft of YAML highlighting

2020-12-25T14:56:49Z