[nightly] Support vim.lsp.config

[ofseed]

Feature description

nvim recently merged a PR aims to replace the lspconfig interface.

It doesn't matter if this interface is not used, as it is just a higher-level interface. However, it would be better to use it because its goal is to provide a set of standardized configurations that allow users to modify and extend, as well as define global configurations.

[mrcjkb]

hey 👋

Thanks for the heads-up. 🙏

At a first glance, vim.lsp.config appears to be modelled after the nvim-lspconfig architecture, which is different from rustaceanvim's.

The global configuration looks interesting.
I think merging a subset of vim.lsp.config configurations with rustaceanvim's config could make sense.
But I most likely won't be changing the architecture of rustaceanvim to use vim.lsp.config. For instance, I would probably ignore the filetypes field, as rustaceanvim uses ftplugin runtime scripts to spin up the LSP client.

[ofseed]

It not only brought these functions but also introduced a new runtime script folder, lsp/, similar to ftplugin/. I think this level of support makes sense for plugins that provide support for a specific language. If rustaceanvim can provide some feedback to upstream, I think that would be great too :)

[mrcjkb]

but also introduced a new runtime script folder, lsp/, similar to ftplugin/

It doesn't look similar to ftplugin/ to me. Rustaceanvim uses ftplugin to start the LSP client so that the plugin does not need to be loaded during startup (unless opening a Rust file).
Thanks to this, if you start Nvim opening a Markdown file, for example, rustaceanvim has zero impact on startup time, no matter which plugin manager you are using. This would not be the case if it used lsp/ or plugin/.

If rustaceanvim can provide some feedback to upstream, I think that would be great too :)

I will have a look at the PR in more detail later. If Nvim provides an API to query the config for a given server, then it should be trivial to add support to rustaceanvim 😄.

[mrcjkb]

As of neovim/neovim#31771, there's a public API to get the resolved config.