fix: filetype patterns with wildcards

[WieeRd]

Problem

While inspecting the generated filetype:servers mapping, I realized there are servers with * wildcards in their filetype patterns.

return {
  filetype_servers = {
    ["*"] = { "typos_lsp" },
    ["*.hl"] = { "hyprls" },
    [".config/hypr/*.conf"] = { "hyprls" },
    ["hypr*.conf"] = { "hyprls" },
  },
}

auto-lsp.nvim cannot deal with these as the filetype lookup is done through simple table indexing.

Solution

• Investigate upstream and find out why exactly those patterns are required.
• Scan through the entire mapping every time.
• Register separate autocmds just for each of those filetypes with wildcards.

[WieeRd]

They were mistakes from upstream.

typos_lsp

The * filetype is unnecessary. Generic servers can just omit filetypes field completely, and lspconfig will launch them upon BufReadPost instead of FileType.

hyprls

hyprland-community/hyprls#11 (comment)

Hi! I actually did a PR for lspconfig to include hyprls (see neovim/nvim-lspconfig#3137) but it's misconfigured: I mistook filetypes for file name patterns...

However someone fixed my mistake lmao, thx @mehalter

So the lspconfig should work if the hyprlang filetype is defined

It was a mistake, and the filetypes with wildcards can be removed completely.

[WieeRd]

• fix: remove invalid filetypes containing wildcards from typos_lsp and hyprls neovim/nvim-lspconfig#3273