LuaLS 'missing fields' in plugin setup calls

[9mm]

Since about a week ago, I have about a dozen plugins which look like this as if they're properly misconfigured.

I was told by @sumneko this the intended behavior, so now my question is... how are you supposed to set up these plugins? I thought under the hood all of these just take the keys you enter and overwrite their default keys, but if this is the desired behavior with LuaLS and not a bug, then does that mean all these plugins are not written correctly? Am I not defining options properly?

• comment.nvim
• lsp-comp
• nvim-surround
• catpuccin theme
• treesitter.config
• ... and more

[komidore64]

This is not a long-term solution, but a quick workaround: I have found that downgrading lua-language-server to 3.6.23 no longer produces the flood of "missing-field" messages.

[sumneko]

It looks like these fields were not marked as optional when the function was defined. Until they are fixed, you can disable this diagnostic using diagnostics.disable.