fix(statusline): display null-ls linters properly #2921
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
null-ls linters may have either
DIAGNOSTIC
,DIAGNOSTIC_ON_OPEN
, orDIAGNOSTIC_ON_SAVE
as its method parameter. e.g., https://github.com/jose-elias-alvarez/null-ls.nvim/blob/8914051a3d399e9715833ad76bbf5fe69ea7faf0/lua/null-ls/builtins/diagnostics/buf.lua#L12Currently, only linters with
DIAGNOSTIC
are shown in the lsp component on the statusline regardless of whether the linters are registered and work properly.This is due to
lvim.lsp.null-ls.linters.list_registers
returning only linters withDIAGNOSTIC
.This PR makes that function retrieve the linters with all three method types and return the merged list.
How Has This Been Tested?
buf
null-ls linter, which is set toDIAGNOSTIC_ON_SAVE
, open a supported file (i.e., proto file), then check ifbuf
linter is shown in the statusline.