https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-9.html#ts-ignore-or-ts-expect-error

Is this what you're looking for?

@DonnieWest this is not a typescript error the tsc doesnt report any errors this is just a diagnostic reported by typescript-language-server and since it is not a real error ts-ignore doesnt really help with that

Coc handles this via a coc-specific configuration setting, when "typescript.suggestionActions.enabled": false, coc will filter out all suggestions (except unused variable, but that's pretty opinionated).

I can take a look at tackling this (it's been bothering me too :P); this could be done via a command line switch like --ignore-diagnostic-code 42 (which could occur multiple times), which would then be used to filter out the diagnostics sent back to neovim.

What do you think @DonnieWest ?

@pyrho sounds like a plan :)

How about block specific ignores? similar to allow macro of rust or ts-ignore annotation of typescript ?

The suggestion in the review was that this should rather be handled in the client itself since diagnostics are a standard LSP feature and there is no reason to implement it per server.

Anyone strongly disagres with that?