-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assistance with adding sonarlint-ls support #520
Comments
Actually looks like sonarlint language server expects this path to be in the
|
@atgote I already tried that. It then tells me about an unsupported message from lsp. I looked into the CoC and Neovim LSP plugins. Seems like they contain a lot of the VSCode plugin code. Not sure if this is even possible sending just stand LSP messages to the server. One of the Sonarqube devs gave some hints here though Here are the logs
|
So the server requires some initialization options. At least the exceptions above are related to missing The following
But.. At the moment we have unexpected warning messages from the server.
|
I've reviewed client (vscode extension) implementation. There is a bunch of custom notifications and requests used by the sonarlint language server (only). Including those highlighted in red in the previous message. |
Meaning it isn't easily possible using the Vim lsp? |
@atgote Sorry, did not see your first message. This actually works and I could successfully load the |
Yes, Some additional functionality should be implemented on top of the existing LSP client to handle the unsupported notifications/messages. Otherwise the server doesn't work. For example we should respond |
Trying to use sonarlint-ls with lsp
There exists a coc plugin and I have tried to the same arguments from here
This is what I have so far
It starts up fine. Sonarlint needs to be informed about the compile_commands.json somehow. No idea how to do that in lsp. For coc I would add this
Server and debug output:
or here in a pastebin: https://0x0.st/XZFy.txt
The text was updated successfully, but these errors were encountered: