Closed mehalter closed 1 month ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[x] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[x] Proper usage of opts
table rather than setting things up with the config
function.
@rafaelderolez @owittek @RayJameson What do you guys think?
I don't code TS/JS, so I can't contribute to this discussion
https://github.com/AstroNvim/astrocommunity/issues/974 is proof that this is the way.
not a fan of typescript-tools so feel free to go ahead
Yeah I second this. Lets go ahead and merge this @mehalter . Typescript-tools is just a pain in the ass at this point.
after updating I can't see inlay hints anymore. Am I missing something?
Hm I thought I configured vtsls with the same inlay hints 🤔 like you don't see them when you toggle them on or you have turned them on by default in AstroLSP? I can check in a bit
After the update, cmp and code actions options are duplicated.
Make sure to uninstall tsserver...
Make sure to uninstall tsserver...
It worked correctly after a clean install. Thanks!
Not sure how but it worked when I installed vtsls
through Mason.
Thank you.
📑 Description
This moves from
typescript-tools.nvim
tovtsls
language server. Let me know if this is desired, I feel liketypescript-tools
always has problems with usersℹ Additional Information