feat: migrate to vim.lsp.config #3659

Problem:
Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy
nvim-lspconfig "framework".

Solution:
Migrate all configs to `lsp/*` variants. The old configs in
`lua/lspconfig/` are "frozen".

The new configs include these changes:
- `commands` field became raw calls to
  `vim.api.nvim_buf_create_user_command` inside `on_attach`.
- `root_dir` became:
  - `root_markers` whenever the file list was simple didn't need to mach `*`
  - if the logic was complicated, or needed to match something like
    '\*.c', it was defined as a vim.lsp.Config `root_dir` callback.
- `on_config_change` became `before_init`. I don't actually know if this
  is the correct approach, but looking around the documentation of
  `nvim-lspconfig` a saw that it was defined as the function that gets
  called as soon as the config have `root_dir`, and so I thought
  `before_init` might be the closest alternative.
- `docs.description` became a luadoc `@brief` docstring.
- `single_file_support = false`?

Co-authored-by: Aliou Diallo <aliou@users.noreply.github.com>
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>

1 files changed, 20 insertions, 0 deletions

diff --git a/lsp/blueprint_ls.lua b/lsp/blueprint_ls.lua
new file mode 100644
index 00000000..365784be
--- /dev/null
+++ b/lsp/blueprint_ls.lua
@@ -0,0 +1,20 @@
+---@brief
+---
+---https://gitlab.gnome.org/jwestman/blueprint-compiler
+--
+-- `blueprint-compiler` can be installed via your system package manager.
+--
+-- Language server for the blueprint markup language, written in python and part
+-- of the blueprint-compiler.
+return {
+  cmd = { 'blueprint-compiler', 'lsp' },
+  cmd_env = {
+    -- Prevent recursive scanning which will cause issues when opening a file
+    -- directly in the home directory (e.g. ~/foo.sh).
+    --
+    -- Default upstream pattern is "**/*@(.sh|.inc|.bash|.command)".
+    GLOB_PATTERN = vim.env.GLOB_PATTERN or '*@(.blp)',
+  },
+  filetypes = { 'blueprint' },
+  root_markers = { '.git' },
+}