tsdoc
neovim
Our great sponsors
tsdoc | neovim | |
---|---|---|
15 | 22 | |
4,655 | 1,933 | |
1.1% | 8.4% | |
6.1 | 8.0 | |
19 days ago | 10 days ago | |
TypeScript | Lua | |
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
-
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 ?
- Do you use JSdocs with TypeScript?
neovim
-
Lualine section separators color
My terminal is iTerm2, I'm using FiraCode nerd font 14pt. I'm using Rose pine colortheme, and this is my config:
-
rose-pine cursor color
Even though I have a white cursor setting on my terminal (iTerm2), setting rose-pine as the colorscheme changes the cursor to a dark grey that's very hard to spot. Anyone knows how to disable this behavior/set it back to white?
-
Need light color scheme
rose-pine with variant "dawn"
-
What color scheme do you use?
I can't get over Rosé Pine
-
how to remove this border overlap?
see rose-pine wikihttps://github.com/rose-pine/neovim/wiki/Recipes
-
Guys can you help me identify which theme is this?
Rose pine
-
Looking for a new colorscheme
Rose-Pine also looks really good
-
How can I stop Treesitter's highlighting overriding spellcheck highlighting?
I am using https://github.com/rose-pine/neovim (🫶) if that has anything to do with it, or if anyone is interested!
-
darkrose.nvim - a low-contrast colorscheme based on rose colors for dark theme lovers
I've decided to release my personal Neovim colorscheme, darkrose.nvim, as a plugin; this is my first one! It is very inspired by rose-pine, but is more of a OLED-type theme, and is very low-contrast. I designed it because I wanted to use my favorite colors in a colorscheme, so I just smashed them together and this is the result. While this is not stable enough to be called 1.0, I believe the colors are stable enough that I can release it and ask for improvements. Breaking changes can still be made until I release a 1.0 version, and I will adhere to semver after that.
-
Newbie here. I am trying to add formatting and linting to my nvim configuration, but null-ls is not reading my .toml files. Does anyone know how to set specific paths for null-ls to read these files? Thanks!
Looks like rose-pine
What are some alternatives?
typedoc - Documentation generator for TypeScript projects.
sonokai-nvim - A personal port of sonokai/monokai theme for neovim using rktjmp/lush
vscode-docthis - JSDoc generator extension for Visual Studio Code.
gruvbox.nvim - Lua port of the most famous vim colorscheme
compodoc - :notebook_with_decorative_cover: The missing documentation tool for your Angular, Nest & Stencil application
oceanic-next - Oceanic Next theme for neovim
redoc - 📘 OpenAPI/Swagger-generated API Reference Documentation
space-vim-theme - :blossom: A dark and light colorscheme for space-vim that supports GUI & terminal
vim-doge - (Do)cumentation (Ge)nerator for nearly 20 languages 📚 Generate proper code documentation with a single keypress. ⚡️🔥
jellybeans-nvim - A port of jellybeans colorscheme for neovim
tree-sitter-comment - Tree-sitter grammar for comment tags like TODO, FIXME(user).
vim-gruvbox8 - A simplified and optimized Gruvbox colorscheme for Vim