nvim-treesitter/queries/smali, branch docs/contrib

feat!: drop modules, general refactor and cleanup

2025-05-12T16:43:40Z

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

2024-03-16T12:51:16Z

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

2024-03-16T12:51:16Z

fix(highlights): improve member/property distinction

2024-01-19T15:58:37Z

fix(highlights): improve consistency

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.

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

chore(smali): add tests

2023-04-25T06:37:31Z

feat(smali): update queries from upstream parser

2023-04-25T06:37:31Z

perf: remove match where possible

2023-04-21T22:24:17Z

refactor(smali): refactor queries from upstream

2023-04-18T02:50:34Z

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

feat: add `@comment.documentation` where applicable

2023-03-05T22:15:32Z

feat(smali): improve queries

2023-02-22T13:11:22Z

refactor: move method and end_method to @keyword.function

2023-01-09T20:24:54Z

fix: character_literal is no longer unsupported :)

2023-01-09T20:24:54Z

feat: add character_literal query

2023-01-09T20:24:54Z

Co-authored-by: ObserverOfTime

feat: add smali query

2023-01-09T20:24:54Z