| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | refactor: Remove all `(ERROR) @error` captures | Pham Huy Hoang | 2023-10-25 | 1 | -2/+0 |
| | | | | | | | | | | | | | 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 `@comment.documentation` where applicable | Amaan Qureshi | 2023-03-05 | 1 | -1/+4 |
| | | |||||
| * | feat!: add `@keyword.coroutine` capture | Amaan Qureshi | 2023-03-03 | 1 | -2/+5 |
| | | |||||
| * | highlights: create subscoping for ternary operator | Stephan Seitz | 2022-12-02 | 1 | -1/+1 |
| | | | | | | | | | | | After https://github.com/nvim-treesitter/nvim-treesitter/issues/470, we decided to use `@conditional` for ternary operator instead of operator despite `@conditional` is documented for keywords only. A sub-scoping can make it easier for people to highlight this operator group differently. Also unify the usage of `@conditional...` across languages. | ||||
| * | highlights(hack): fix captures | ObserverOfTime | 2022-11-26 | 1 | -15/+24 |
| | | |||||
| * | highlights(hack): use `@function.call`/`@method.call` | Stephan Seitz | 2022-09-11 | 1 | -3/+3 |
| | | |||||
| * | highlights(hack): fix typo in "tuple" keyword | Stephan Seitz | 2022-04-06 | 1 | -1/+1 |
| | | | | | https://github.com/slackhq/tree-sitter-hack/pull/34 | ||||
| * | highlights(hack): add keywords implements | Stephan Seitz | 2022-01-17 | 1 | -3/+11 |
| | | |||||
| * | highlights(hack): extend queries add tests | Stephan Seitz | 2022-01-17 | 1 | -5/+137 |
| | | |||||
| * | highlights(hack): add some basic highlights | Stephan Seitz | 2022-01-17 | 1 | -0/+162 |
| Fixes #2041 | |||||
