What does resolved_capabilities mean for null-ls ?

[aitvann]

I've seen this snippet of code from you, and I'm wondering why this isn't the default behavior? It makes a lot more sense to me. I mean, what's the point of client.resolved_capabilities.document_formatting then if it doesn't mean null-ls can format a document?

[jose-elias-alvarez]

There's 2 things going on:

1. null-ls declares its capabilities on launch. Here, it declares all of its capabilities, regardless of which sources a user has actually registered. Neovim resolves these (hence the name) and assigns them to client.resolved_capabilities.
2. When sending a request, Neovim checks whether each client can support the request using client.supports_method(). Since at this point we know what null-ls can and can't do based on registered sources, we can respond accurately.

The user's request in the linked issue was based on a special case where they wanted to register a source that's enabled for all filetypes but disable it under specific conditions. I recommended using client.supports_method(), and in the end 0a8bf7b added the ability to explicitly disable a capability, too.

The LSP specification defines a way for servers to send capabilities dynamically, but it's not (yet) supported by Neovim.

[aitvann]

Oh I see it's nvim's limitation. Thank you for your answer and for such an awesome plugin !