nvim-treesitter/queries/jsonnet, branch fix/lua[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/jsonnet?h=fix%2Flua2025-05-12T16:43:40Zfeat!: drop modules, general refactor and cleanup2025-05-12T16:43:40ZChristian Clasonc.clason@uni-graz.at2023-06-12T15:54:30Zurn:sha1:692b051b09935653befdb8f7ba8afdb640adf17brefactor(queries): Remove quotes from properties in set! directive2024-07-28T09:43:41ZOmar Valdezomarantoniovaldezf2@gmail.com2024-07-27T23:28:19Zurn:sha1:51bba660a89e0027929206b622c9c1cbdd995cfbfeat: more comment injections2024-06-15T08:40:34ZRiley Bruinsribru17@hotmail.com2024-06-08T04:33:49Zurn:sha1:9d68e876cce94fc9f8f8819da0c956a4429a3766refactor(format): drop extra indentation for field2024-03-21T14:51:26ZPhạm Huy Hoànghoangtun0810@gmail.com2024-03-21T11:44:35Zurn:sha1:722617e6726c1508adadf83d531f54987c703be0feat(highlights)!: enforce documented captures (#6232)2024-03-03T10:00:11ZChristian Clasonc.clason@uni-graz.at2024-03-03T10:00:11Zurn:sha1:99ddf573531c4dbe53f743ecbc1595af5eb1d32f
Problem: Allowing undocumented "secret" (sub)captures makes it harder
to write comprehensive colorschemes and catch inconsistent captures.
Solution: Only allow captures listed in CONTRIBUTING.md. Add useful
(cross-language) subcaptures and drop language-specific or too niche
ones.
Follow-up: Adding further `*.builtin` captures and changing queries to
use them.
Language-specific subcaptures should instead be added in user config or
a custom language plugin.
chore: query formatting2024-01-19T15:58:37ZPham Huy Hoanghoangtun0810@gmail.com2024-01-06T06:05:50Zurn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9feat!: align standard captures with upstream2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-12-24T09:00:20Zurn:sha1:1ae9b0e4558fe7868f8cda2db65239cfb14836d0
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 captures2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-07-22T13:29:32Zurn:sha1:5b90ea2abaa4303b9205b5c9002a8cdd0acd11a5refactor: Remove all `(ERROR) @error` captures2023-10-25T16:18:50ZPham Huy Hoanghoangtun0810@gmail.com2023-10-25T07:45:14Zurn:sha1:107e61afb7129d637ea6c3c68b97a22194b0bf16
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.
feat: @spell on comments2023-09-12T15:34:58ZJaehwang Jungtomtomjhj@gmail.com2023-09-12T15:25:01Zurn:sha1:9567185621e532a9e29a671c66a11011334b80eafeat(jsonnet): update parser and queries2023-08-25T17:55:22ZJeroen Op 't Eyndejeroen@simplistic.be2023-08-25T17:55:22Zurn:sha1:4d41d9bfb09dd0836ce6910404e3cd570500c9cafeat: update jsonnet queries2023-08-18T01:46:33ZCezary Drożakcezary@drozak.net2023-08-17T18:36:10Zurn:sha1:4ffdc4c985fb1054fb3bfa51c28917e2d9804ca3feat(jsonnet): add "for" & "function", update operator highlights2023-06-08T14:13:26ZHoang Nguyenfolliekazetani@protonmail.com2023-06-08T14:13:26Zurn:sha1:71bb1da621a48856c7f8ca10e674f2ac8c0a9005
`expr` -> `operator` doesn't exist in the node tree anymore after
https://github.com/sourcegraph/tree-sitter-jsonnet/commit/505f5bd90053ae895aa3d6f2bac8071dd9abd8b2feat: add jsonnet2022-09-10T18:09:10ZCezary Drożakcezdro@alatek.com.pl2022-09-07T08:30:43Zurn:sha1:f2d3d509d95943c00975c8a83dbb35907262e30b