Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stsewd/tree-sitter-comment
Tree-sitter grammar for comment tags like TODO, FIXME(user).
https://github.com/stsewd/tree-sitter-comment
comment-tag comments tree-sitter tree-sitter-parser
Last synced: 7 days ago
JSON representation
Tree-sitter grammar for comment tags like TODO, FIXME(user).
- Host: GitHub
- URL: https://github.com/stsewd/tree-sitter-comment
- Owner: stsewd
- License: mit
- Created: 2021-01-31T02:14:58.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2024-08-24T16:18:43.000Z (5 months ago)
- Last Synced: 2025-01-13T06:02:14.630Z (14 days ago)
- Topics: comment-tag, comments, tree-sitter, tree-sitter-parser
- Language: C
- Homepage: https://stsewd.dev/tree-sitter-comment/
- Size: 408 KB
- Stars: 138
- Watchers: 3
- Forks: 10
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# tree-sitter-comment
[](https://github.com/stsewd/tree-sitter-comment/actions?query=workflow%3ACI+branch%3Amaster)
[Tree-sitter](https://github.com/tree-sitter/tree-sitter) grammar for comment tags like `TODO:`, `FIXME(user):`, etc.
Useful to be embedded inside comments.
Check the playground at .
## Syntax
Since comment tags aren't a programming language or have a standard,
I have chosen to follow popular conventions for the syntax.
### Comment tags
* Comment tags can contain:
- Upper case ascii letters
- Numbers (can't start with one)
- `-`, `_` (they can't start or end with these characters)
* Optionally can have an user linked to the tag inside parentheses `()`
* The name must be followed by `:` and a whitespace
### URIs
* http and https links are recognized
If you think there are other popular conventions this syntax doesn't cover,
feel free to open a issue.
## Examples
```
TODO: something needs to be done
TODO(stsewd): something needs to be done by @stsewd
XXX: fix something else.
XXX: extra white spaces.
(NOTE: this works too).
NOTE-BUG (stsewd): tags can be separated by `-`
NOTE_BUG: or by `_`.
This will be recognized as a URI
https://github.com/stsewd/
```
## FAQ
### Can I match a tag that doesn't end in `:`, like `TODO`?
This grammar doesn't provide a specific token for it,
but you can match it with this query:
```scm
("text" @todo
(#eq? @todo "TODO"))
```
### Can I highlight references to issues, PRs, MRs, like `#10` or `!10`?
This grammar doesn't provide a specific token for it,
but you can match it with this query:
```scm
("text" @issue
(#match? @issue "^#[0-9]+$"))
;; NOTE: This matches `!10` and `! 10`.
("text" @symbol . "text" @issue
(#eq? @symbol "!")
(#match? @issue "^[0-9]+$"))
```
### I'm using Neovim and don't see all tags highlighted
To avoid false positives, Neovim doesn't highlight all tags,
but a list of specific ones,
see the list at [`queries/comment/highlights.scm`](https://github.com/nvim-treesitter/nvim-treesitter/blob/master/queries/comment/highlights.scm).
If you want your tag highlighted, you can extend the query locally, see `:h treesitter-query`.
Or if you think it's very common, you can suggest it [upstream](https://github.com/nvim-treesitter/nvim-treesitter).
## Why C?
Tree-sitter is a [LR parser](https://en.wikipedia.org/wiki/LR_parser) for context-free grammars,
that means it works great for grammars that don't require backtracking,
or to keep a state for whitespaces (like indentation).
For these reasons, parsing _languages_ that need to keep a state or falling back to a general token,
it requires some manual parsing in C.
## Projects using this grammar
- [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter)
- [helix](https://github.com/helix-editor/helix)
- Yours?
## Other grammars
- [tree-sitter-rst](https://github.com/stsewd/tree-sitter-rst): reStructuredText grammar.