Disable harper or particular linters for certain filetypes / modify code actions

[michaelrommel]

I tried to enable harper only for markdown files by using:

require("lspconfig").harper_ls.setup({
	filetypes = { "markdown" },
	...
})

but that did not work. How would one enable or disable harper only for certain filetypes?

Second question: would it be possible to deactivate some linters only in some filetypes, e.g. disable SpellCheck for programming languages but keep SpellCheck on for markdown or text files?

Is it possible to programmatically start code actions, like adding a word to one of the dictionaries? Currently it seems, that only if harper offers the addition itself, it can be chosen. So e.g. if a term "T&C" triggers an error on "C" I cannot easily add the phrase to a dictionary except editing the user dictionary myself.

I tried searching the open and closed issues and discussions and did not find any answer. Please tell me if I missed a thread. Thanks!

[hippietrail]

So e.g. if a term "T&C" triggers an error on "C" I cannot easily add the phrase to a dictionary except editing the user dictionary myself.

Not the answer to your issue but related to this specific comment: #743

[elijah-potter]

Hey @michaelrommel. I'd love to get your problem fixed. I'll address your issues one at a time:

How would one enable or disable Harper only for certain filetypes?

Your configuration is working for me. Are you running the latest version of harper-ls?

Second question: would it be possible to deactivate some linters only in some filetypes, e.g. disable SpellCheck for programming languages but keep SpellCheck on for markdown or text files?

This is not currently supported in harper-ls. If you'd like for it to happen, go ahead and open an issue for it.

[michaelrommel]

Thank you for your quick response. I was on the latest version, but based on your statement, that it should be working, I reconfigured my neovim config, as it turned out, that mason-lspconfig started the server, even though it should not have. I moved everything to a normal nvim-lspconfig and now harper only starts for the filetypes given. Thanks for the hint. Again one plugin less...

For the second item, I see that there is already a lot in the backlog. I think my request would only make things more complicated and do not want to raise such an issue. I have activated harper now only for markdown, text and gitcommits. The normal code base comments probably do not need much of harper's attention.

Thanks and I am looking forward, what you will do with this plugin, I think it has great potential.

Michael.