Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lsp4e-dev] LSP diagnostics don't seem to be supported when integrating with Eclipse

Hello,

On Thu, Mar 2, 2023 at 12:12 PM Balog Tamás via lsp4e-dev <lsp4e-dev@xxxxxxxxxxx> wrote:
Our language server is implemented in TypeScript with the vscode-language-server-node package, so I'm executing a Node process from the Eclipse plugin. I see that the Node process starts properly, but when I inspect the client capabilities in the connection's InitializeParams, I see that both the textDocument/publishDiagnostics and the pull diagnostic related capabilities are false, meaning they are not supported by the client application (Eclipse).

pullDiagnostics and also newer capabilities for publishDiagnostics are indeed not supported. Please open an issue about it against the GitHub project, and consider contributing related work. 

I find this odd considering that there are other language server integrations for Eclipse that work with diagnostics. I'm completely new to Eclipse plugin development, so, I don't know if I'm missing something, or misconfigured something.

Most language servers use the `publishDiagnostics`. This is part of the very first version of LSP specification and there is no capability to enable it or not; LSs are supposed to send them anyway. The capability are not toggling usage of publishDiagnostics, they only inform about some newer capabilities being supported or not.

HTH


Back to the top