File level diagnostics and status line provider info

[mnarrell]

I'm not able to display any file-level diagnostics with plugins like telescope.nvim or trouble.nvim. null-ls diagnostics only appear at the workspace/project level. Additionally, I don't see any diagnostic counts in my status line from either galaxyline.nvim or feline.nvim. I'm using null_ls.builtins.diagnostics.markdownlint for this, but other builtins seem to have the same behavior (null_ls.builtins.diagnostics.golangci_lint)

I'm building Neovim from source off master and running this configuration:

local null_ls = require "null-ls"
null_ls.config {
	debug = true,
	diagnostics_format = "[#{c}] #{m} (#{s})",
	sources = {

		-- Go
		null_ls.builtins.diagnostics.golangci_lint,
		null_ls.builtins.diagnostics.staticcheck,

		-- Markdown
		null_ls.builtins.diagnostics.markdownlint,
		null_ls.builtins.code_actions.proselint,

	},
}

require("lspconfig.configs")["null-ls"].setup()

Do I have something misconfigured?

[jose-elias-alvarez]

This is because both plugins are using vim.lsp.diagnostic instead of the new vim.diagnostic API, which is an issue because null-ls no longer uses its client namespace (each source gets its own). Getting workspace / project-level diagnostics still works because it doesn't specify a namespace.

The old API is deprecated, so it's a question of when the plugins are able to update. Relevant issues: nvim-telescope/telescope.nvim#1581 and folke/trouble.nvim#133

[mnarrell]

Makes sense. Thanks for the quick response.