and all the examples I find are for lazy not pack.
I don't understand since the only difference should be the path which I updated from the lazy install location to the pack one.
---@type vim.lsp.Config
return {
cmd = { 'lua-language-server' },
filetypes = { 'lua' },
root_markers = { '.luarc.json', '.luarc.jsonc' },
---@type lspconfig.settings.lua_ls
settings = {
Lua = {
runtime = {
version = 'LuaJIT'
},
diagnostics = {
globals = { 'vim', 'lspconfig' }
},
workspace = {
library = {
vim.env.VIMRUNTIME,
vim.fn.stdpath("data") .. "/site/pack/core/opt/nvim-lspconfig"
}
}
}
}
}
Is anyone else using pack with lspconfig and if so how are you doing this?
I want to be able to validate my lsp config settings and get all the other shit that comes with it like autocomplete and documentation for LSP configuration fields, etc.
I can't figure out why it's not able to find the annotations like: `---@type lspconfig.settings.lua_ls`