nvim-treesitter/queries/solidity, branch master[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/solidity?h=master2025-05-12T16:43:30Zfeat(solidity): add doxygen injections (#7853)2025-05-12T16:43:30ZLeoleonard.paturel@openzeppelin.com2025-05-12T16:43:30Zurn:sha1:066fd6505377e3fd4aa219e61ce94c2b8bdb0b79feat(solidity): add `abstract` keyword2025-05-12T16:43:10ZLeoleonard.paturel@openzeppelin.com2025-05-12T16:43:10Zurn:sha1:0484f881c66fcac9ac517a5e62d99093e2e3702bfix(solidity): remove spurious operators in highlight queries (#7412)2024-11-27T10:04:28ZJoranHonigJoranHonig@users.noreply.github.com2024-11-27T10:04:28Zurn:sha1:8d4fdc5e47e2a4e00179e43f56221250ce365973feat: more comment injections2024-06-15T08:40:34ZRiley Bruinsribru17@hotmail.com2024-06-08T04:33:49Zurn:sha1:9d68e876cce94fc9f8f8819da0c956a4429a3766fix(solidity): re-enable unbroken operators2024-05-26T09:59:56ZChristian Clasonc.clason@uni-graz.at2024-05-26T09:29:35Zurn:sha1:ba149fa3b100bb05ff0185dd5e644f455e6696bffix(solidity): disable broken operators2024-05-12T08:10:03ZChristian Clasonc.clason@uni-graz.at2024-05-12T08:08:06Zurn:sha1:c4f65272a971b9d5d6ac7ed4607e50dd6207923ffeat: more `@keyword.type` captures2024-05-01T07:59:50ZRiley Bruinsribru17@hotmail.com2024-04-23T19:23:15Zurn:sha1:f58cae6c228e26681039253cb172de16cd764408fix(solidity): adapt queries to parser changes2024-04-13T18:04:38ZJoranHonigJoranHonig@users.noreply.github.com2024-04-13T16:46:25Zurn:sha1:3e1d836e0e5abe5c47d0cef67d51494e2e48d7bafix(solidity): update queries from upstream (#6424)2024-04-10T07:22:05ZAmaan Qureshiamaanq12@gmail.com2024-04-10T07:22:05Zurn:sha1:d90e11756da30959da59eeb8888ecf16e877d86afeat(highlights)!: `@keyword.storage` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-16T05:23:57Zurn:sha1:dccf31f9b1fbbbd09e6720c7d8f5f1a2433fd32dfeat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-08T10:09:51Zurn:sha1:998b230a77b544761bae8aa7518d40b91a5c9559chore: 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`
refactor: 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: add solidity folds2023-10-21T18:40:19ZMeet Mangukiyameet@flamy.dev2023-10-17T16:57:03Zurn:sha1:cffa252f5e8f257d4952c0817c44fdaefd2c25a7solidity: Update highlights.scm (#5453)2023-09-27T06:08:46Zzeroknots102132718+zeroknots@users.noreply.github.com2023-09-27T06:08:46Zurn:sha1:86d0b2b1c08ff93020b261fc96201b25eb3a9082
https://soliditylang.org/blog/2021/04/21/custom-errors/
error keyword was introduced in 0.8.4fix(solidity): variable should not match last, tidy up highlights2023-04-25T18:19:44ZAmaan Qureshiamaanq12@gmail.com2023-04-25T17:09:18Zurn:sha1:82bcd8483e0b802bd5f639046c88aecfddbab508fix: revert for solidity2023-03-21T06:23:52ZZhizhen Hehezhizhen.yi@gmail.com2023-03-21T06:19:12Zurn:sha1:181a580190d4684d5f6e34c500c0aa99258a04d1docs: fix typo2023-03-21T06:23:52ZZhizhen Hehezhizhen.yi@gmail.com2023-03-21T05:50:54Zurn:sha1:a1df50a79f0e422b3c99680071f32994893f3a3dfeat: add `@comment.documentation` where applicable2023-03-05T22:15:32ZAmaan Qureshiamaanq12@gmail.com2023-03-02T13:06:35Zurn:sha1:5a87bc98dabd0d38152a6fa774005f7ecbd40f1bfeat(solidity): use maintained parser and update highlights accordingly2023-02-24T21:05:33ZAmaan Qureshiamaanq12@gmail.com2023-02-24T12:42:04Zurn:sha1:5c511dd1244fc8eeccf8920a5a4754ae01da296edocs: fix typos2023-02-23T19:39:43Zdundargocgocdundar@gmail.com2023-02-23T19:30:36Zurn:sha1:4612212c72a3fe683cbca2f99977ad63b942f70ehighlights(solidity): use more specific groups2022-11-26T11:17:51ZObserverOfTimechronobserver@disroot.org2022-10-28T14:26:32Zurn:sha1:08bd9d0e088aefa7eb9c1ccf773e2c0f477eeaa3highlights(solidity): use `@function.call`/`@method.call`2022-09-11T11:16:06ZStephan Seitzstephan.seitz@fau.de2022-08-29T21:49:15Zurn:sha1:f9d1c68cf96c97441e17e01408a89d3e044dd683Refactor solidity highlights.scm further2022-03-11T18:06:39ZYongJieYongJieKhooYongJie@gmx.com2022-03-11T17:11:17Zurn:sha1:fc0b881f93851a79ae3506d54e0e3e368c98ce58
- Instead of @keyword, use @conditional, @exception, @return, @function
as appropriate
- Standardize to using @field (instead of @property)for struct members
Refactor solidity highlights.scm2022-03-11T18:06:39ZYongJieYongJieKhooYongJie@gmx.com2022-03-10T21:07:26Zurn:sha1:8f3991065d4753c4b458fb19b9a2332f3d740c50
- Use more specific/appropriate captures; change invalid captures
- Don't highlight punctuations in type names (e.g., the brackets in
'bytes32[]')
Add highlights query for Solidity2022-03-11T18:06:39ZYongJieYongJieKhooYongJie@gmx.com2022-03-10T11:14:49Zurn:sha1:a180859eeadd52c05745022064ff423423c17bb5