Question about setup_handlers()
#51
-
Here's the snippets: require("mason-null-ls").setup({
ensure_installed = require("core.settings").null_ls,
automatic_installation = true,
automatic_setup = true,
})
require("null-ls").setup({
debug = false,
update_in_insert = false,
diagnostics_format = "[#{c}] #{m} (#{s})",
-- NOTE: Users don't need to specify null-ls sources if using only default config.
-- "mason-null-ls" will auto-setup for users.
sources = {
-- formatting
btn.formatting.black.with({ extra_args = { "--fast" } }),
btn.formatting.markdownlint,
-- diagnostics
btn.diagnostics.shellcheck.with({ diagnostics_format = "#{m} [#{c}]" }),
btn.diagnostics.markdownlint.with({ extra_args = { "--disable MD033" } }),
},
})
require("mason-null-ls").setup_handlers() |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hmmm, I am not actually sure what happens when require("null-ls").setup()
require("mason-null-ls").setup(
{
ensure_installed = require("core.settings").null_ls,
automatic_setup = true,
}
)
require("mason-null-ls").setup_handlers(
{
shellcheck = function()
null_ls.register(null_ls.builtins.diagnostics.shellcheck.with({diagnostics_format = "#{m} [#(c)]"}))
end,
}
)
|
Beta Was this translation helpful? Give feedback.
Hmmm, I am not actually sure what happens when
null-ls.registeris called for the same exact source.mason-null-lswill attempt to re-register though. I just don't know hownull-lshandles that. However, I recommend you use eithernull-lsormason-null-lsto set up and not both.