You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that #2885 has been merged, we can clean up a bunch of language server configs that had to manually specify priorities of patterns for finding the root directory. For example, in tsserver, this
Language server
No response
Requested feature
Now that #2885 has been merged, we can clean up a bunch of language server configs that had to manually specify priorities of patterns for finding the root directory. For example, in
tsserver
, thisnvim-lspconfig/lua/lspconfig/server_configurations/tsserver.lua
Lines 15 to 18 in 90a28fd
can simply become
Anywhere where a language server has something like
return util.root_pattern(pattern1) or util.root_pattern(pattern2) or ...
can be simplified.Here's a list of language servers I've identified:
nvim-lspconfig/lua/lspconfig/server_configurations/cairo_ls.lua
Lines 11 to 14 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/custom_elements_ls.lua
Lines 7 to 10 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/gopls.lua
Line 23 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/gradle_ls.lua
Line 20 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/hls.lua
Lines 8 to 11 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/kotlin_language_server.lua
Line 29 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/omnisharp.lua
Lines 41 to 49 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/syntax_tree.lua
Line 8 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/tailwindcss.lua
Lines 103 to 106 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/tsserver.lua
Lines 15 to 18 in 7384e71
nvim-lspconfig/lua/lspconfig/server_configurations/vtsls.lua
Lines 14 to 17 in 7384e71
Let me know if I have missed any.
cc @glepnir @justinmk
Other clients which have this feature
No response
The text was updated successfully, but these errors were encountered: