You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 12, 2023. It is now read-only.
Neovim currently doesn't have support for dynamic capability registration, though there is an open PR. Supporting it will let the null-ls server start up with no capabilities, then register its actual capabilities based on a user's registered sources.
In the meantime, I want to improve the way null-ls handles requests to avoid cases like this one, where null-ls is listed as a formatting source even though it can't provide formatting for a filetype (diagnostics and code actions are fine, since an empty response doesn't do anything negative). My tentative idea is to override client.supports_method, which I think should let us catch this earlier, but I need to look into this a bit more when I have time.
The text was updated successfully, but these errors were encountered:
Neovim currently doesn't have support for dynamic capability registration, though there is an open PR. Supporting it will let the null-ls server start up with no capabilities, then register its actual capabilities based on a user's registered sources.
In the meantime, I want to improve the way null-ls handles requests to avoid cases like this one, where null-ls is listed as a formatting source even though it can't provide formatting for a filetype (diagnostics and code actions are fine, since an empty response doesn't do anything negative). My tentative idea is to override
client.supports_method
, which I think should let us catch this earlier, but I need to look into this a bit more when I have time.The text was updated successfully, but these errors were encountered: