nvim-treesitter/queries/http, branch v0.10.0

feat(http): fold queries

2025-01-10T08:06:34Z

feat(http): more comprehensive highlights

2024-11-22T07:56:14Z

fix(http): update injections queries (#7078)

2024-08-31T16:52:23Z

feat(http): switch to new parser version (#7063)

2024-08-21T07:08:45Z

feat(http): update queries to parser changes (#6467)

2024-04-19T07:24:29Z

feat(http): switch to new parser version

2024-03-17T22:46:59Z

fix(http): use `@variable.member` for fields fix(http): keep the comment injection fix(http): keep `method` capture as `@function.method` docs(README.md): update HTTP parser maintainers list feat(http): remove redundant captures cleanup(http): remove unneedeed highlighting captures

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`

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.

feat: add xml & dtd parsers

2023-08-13T07:34:57Z

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

feat(http): update parser queries from upstream

2023-04-20T09:50:08Z

injections(http): add comment injection

2021-11-12T20:52:50Z

refactor: inherit json

2021-11-12T20:52:50Z

fix: address change requests

2021-11-12T20:52:50Z

feat: add http parser

2021-11-12T20:52:50Z

All credit goes to @NTBBloodbath. See: https://github.com/NTBBloodbath/rest.nvim/issues/75#issuecomment-960447966 Co-authored-by: NTBBloodbath