Fix(volar.lsp): Recent renaming of volar-lsp to vue_ls broke resolving of config on fresh installs

[gx089]

Recent changes of renaming of volar-lsp to vue_ls-lsp broke config resolving on fresh installs. There is no vue_ls.lua config.
Fix is, to create a config with name vue_ls.lua.(Is a copy of the volar.lua)

Btw. The official name of the Vue-LSP is Volar. That's because, there was an much older/obsolete lsp called vetur for vue, that isn't used anymore. In my opinion the recent renaming of lsp and mason packages is confusing. but anyway...

neovim/nvim-lspconfig:
#3843

mason-registry:
mason-org/mason-registry#10150

[justinmk]

? #3843 did not change anything in lua/lspconfig/configs/.

cc @Jak-Ch-ll

[gx089]

? #3843 did not change anything in lua/lspconfig/configs/.

cc @Jak-Ch-ll

First of all, we should clarify which behaviour we want to achieve.

1. Intuitive install and configuration steps with the same name, like it's done for other tools/lsp:

require("mason-lspconfig").setup({
	ensure_installed = {
		"vue_ls",
		-- ....
	},
})
lspconfig['vue_ls'].setup({
	-- config override
})

3. Mason-Install with 'vue_ls' and lspconfig-override with 'volar', as it is now necessary, after the recent renaming.
4. Mason-Install with 'volar' and lspconfig-override with 'volar', as it was before the renaming of the lsp (intuitive way of doing it with an uniform name)

Current setups are already broken, because 'volar' is already renamed and doesn't exist in the Mason-Registry anymore!!
So for fresh installations, with your current config, you have to change your ensured_installed from volar to vue_ls manually, if you don't install it via the ui.
Most of us don't install pkgs via the Mason-UI but with ensured_installed.

So in any case, you have to change your config (ensured_installed) after the recent renaming.
An uniform name is more intuitive and should be the preferred way... different names are misleading
The additional 'configs/vue_ls.lua' would solve some headache. I would prefer this way, because you have some kind of backwards compatibility... 1) and 2) works with this. I don't see any benefits but disadvantages in the recent renaming.

What do you think?

[justinmk]

Again lua/lspconfig/configs/ is irrelevant; those are the old, frozen configs for Nvim 0.10.

If there's a change needed in lsp/, propose one. I don't care about any of this because I don't use these configs.

[gx089]

Got ya.
So, the issue was that my setup was using the "old" lspconfig-methods.
For anyone facing the same issue, use the following.

lspconfig['vue_ls'].setup({
-- .... fetches configs for neovim 0.10 // mostly works, but configs are frozen/won't be updated
})

vim.lsp.config('vue_ls', {
-- .... fetches configs for neovim 0.11 // uses the current, updated configs
})

Thanks @justinmk