Prevent null ls from attaching to buffer

[jacksonludwig]

With eslint settings disabled, null-ls is still attaching to ts/js buffers. Is there a way to prevent ts-utils from starting null-ls?

This causing issues when, for example, using the eslint language server. The on_attach of both servers will run, potentially causing conflicting settings/keybinds.

I am using null-ls for other filetypes, so I must call require('lspconfig')['null-ls'].setup({...}). What would you think about something like a null_ls_integrations option?

[jose-elias-alvarez]

We have an option, eslint_enable_code_actions, which is set to true by default. If that option, eslint_enable_diagnostics, and enable_formatting are all set to false, then no null-ls integrations will be registered and the client won't attach:

local lspconfig = require("lspconfig")
lspconfig.tsserver.setup({
    on_attach = function()
        require("nvim-lsp-ts-utils").setup({ eslint_enable_code_actions = false })
    end,
})

require("null-ls").config({})
lspconfig["null-ls"].setup({})

If it's attaching, it's either something else in your null-ls config (e.g. a source that's active for all filetypes) or a bug. Could you try the minimal config above? We could add an option to explicitly disable integrations, since having code actions enabled by default is a relic of how this plugin used to work, but it shouldn't be happening.

[jacksonludwig]

thanks it was my mistake, I had disabled the eslint options I had in my config, but totally missed the eslint_enable_code_actions option as I wasn't setting it explicitly.