| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* fix(format): newline between top-level field defs
* fixup: newline between node and comment
* fixup: optimize pattern
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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`
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
Signed-off-by: Michael Hoffmann <mhoffm@posteo.de>
|
| |
|
|
|
|
|
|
| |
update CONTRIBUTING.md
adjust indents for bass
fix doc capture comment
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
```
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
```
|
| |
|
|
| |
This reverts commit 4a7a713c527f57c355bc817f16fc6d955b8cce9b.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
| |
Closes https://github.com/nvim-treesitter/nvim-treesitter-refactor/issues/18
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
Closes #236
|
| |
|
|
| |
This is so incremental selection works
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
