tsdoc
tree-sitter-comment
tsdoc | tree-sitter-comment | |
---|---|---|
16 | 6 | |
4,787 | 139 | |
0.3% | 2.2% | |
7.6 | 4.7 | |
about 2 months ago | 6 months ago | |
TypeScript | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tsdoc
-
Taking LLMs to (code) town - part II. Creating a vanilla.js web component toolchain from ground up
TSDoc Parser
-
Jsdoc Cheatsheet
For what it’s worth, there’s also TSDoc[1] which is TypeScript’s sorta-equivalent spiritual successor, and notably uses the same format as JSDoc. Inline type annotation is great—and I vastly prefer it to JSDoc as a type annotation mechanism—but supporting the breadth of documentation capability in an inline code position would probably be unwieldy no matter how you try to accommodate it.
1: https://tsdoc.org/
-
What am I Missing (or Could Benefit From Using) For My Stack?
Docs? TSdoc + TypeDoc or DocFX. Of particular interest, this can be used to generate JSON schema's, useful for REST / GraphQL
-
Complete rewrite of ESLint (GitHub discussion by the creator)
Nope, they look the same, at a glance, but they're not the same. JSDoc and TSDoc are different standards, developed by different teams.
- tsc doesn't convert jsdoc types into real typescript
-
How to properly document components
JSDoc is a terrible standard. I would rather go for TypeScript + TSDoc, then use TypDoc to generate the actual documentation based on TS typings. Alternatively, you can go for Vue Styleguidist. It's an excellent tool, but, opposite to TSDoc it's not a standard, it's just a tool.
-
Using @microsoft/tsdoc for documenting functions
I am trying to use the @microsoft/tsdoc package to generate documentation for a given file. I followed the demo that hey have provided https://github.com/microsoft/tsdoc/tree/main/api-demo and it works for the sample input they provided, shown below.
-
Is it better to use the JSDoc return type or TypeScript return type?
Maybe this is of interest? https://tsdoc.org/
- TSDoc – Documentation Your TypeScript in Code
-
Neogen - The annotation toolkit you never knew you needed
Awesome, thank you! Would you be willing to support TSDoc ?
tree-sitter-comment
-
Documentation Comment highlighting with TreeSitter
As far as I know there is currently no treesitter parser for Doxygen style comments. There is a language agnostic comment parser that is supported by nvim-treesitter that will highlight things like TODO: and NOTE: in comments. Until this recent commit nvim-treesitter provided a query for this parser that highlighted @ text in comments. It was meant to highlight a reference to a user but it doubled as a doxygen tag highlight for me for a while. I just noticed that this query has been removed and I'm not sure why but you can add it as a custom query in your Neovim config. I have yet to try this so you'll have to refer to the Neovim treesitter docs for where to add the query.
-
emacs-29: Using treesitter to highlight keywords in comments
I'm not sure how to use this in Emacs, but there's also a tree-sitter grammar specifically for comment blocks, including TODOs: https://github.com/stsewd/tree-sitter-comment
-
Will Treesitter ever be stable on big files?
you mean this one? https://github.com/stsewd/tree-sitter-comment
-
paint.nvim: Simple Neovim plugin to easily add additional highlights to your buffers
The reason I implemented this is because of the slow performance of tree-sitter-comment in large files. Treesitter will inject the comment language for every line comment, which is far from ideal. I've disabled the comment parser, but still wanted to see @something highlighted in Lua comments.
-
Treesitter query not working
The right most window shows the code I want to query. This is a .cpp file, so the main-language is C++. For highlighting the two comments, I'm using tree-sitter-comment. This plugin injects the comment-language. I want to query all tag nodes from this injected language, but this query does not work.
-
Is it possible to get highlight on these comments docs with treesitter?
You can install this parser for treesitter which highlights comments :)
What are some alternatives?
typedoc - Documentation generator for TypeScript projects.
tree-sitter-go-template - Golang template grammar for tree-sitter
compodoc - :notebook_with_decorative_cover: The missing documentation tool for your Angular, Nest & Stencil application
giscus - A comment system powered by GitHub Discussions. :octocat: :speech_balloon: :gem:
neogen - A better annotation generator. Supports multiple languages and annotation conventions.
comments - Native comments for your Laravel application.
vscode-docthis - JSDoc generator extension for Visual Studio Code.
DoxyGen-Syntax - DoxyGen Highlighting on top of c/c++/java
vim-doge - (Do)cumentation (Ge)nerator for nearly 20 languages 📚 Generate proper code documentation with a single keypress. ⚡️🔥
tree-sitter-hcl - HCL grammar for tree-sitter
ts-morph - TypeScript Compiler API wrapper for static analysis and programmatic code changes.
tree-sitter-embedded-template - Tree-sitter grammar for embedded template languages like ERB, EJS