Support for jedi-language-server code diagnostics configuration

Description

Dear @krassowski , after the improvements achieved with jedi-language-server for autocompletion (#272), I am looking forward to configuring it to work with the code diagnostics features.

Unfortunately the latter doesn’t work out of the box and I can’t find any useful debugging/troubleshooting message to share.

Would it be possible to get some help to understand what code diagnostics expects and how to include its configuration? Many thanks

Reproduce

1. Install jedi-language-server as described in https://github.com/pappasam/jedi-language-server
2. Create a minimal server setting (See #272 for example)
3. Make a PEP8 mistake in the code

Expected behavior

Expecting seeing the Diagnostic Panel getting populated. Instead nothing happens.

Thanks!

[krassowski]

This is expected, jedi-language-server only provides syntax errors. Good to have a confirmation that it is working well. We still intend to allow for having two different language servers per document (so that you could use completions from jedi-language-server and diagnostics from another language server) but this has no ETA (it would require some back-and-forth with design and thorough testing so it might happen during one of the future holidays unless someone will contribute earlier).

We just released jupyterlab-lsp 3.3.0 and jupyter-lsp 1.1.2 which bring more stability and performance improvements.

[sntgluca]

@krassowski,

I actually didn’t answer your question below, did I? In my setup, I am using jupyterlab-lsp==3.2.0, jedi-language-server==0.21.0 and pygls==0.9.1, which seem to be the newest public releases (at least with conda).

The diagnostics panel only shows syntax errors. Do I have to change anything? Dependencies, configurations, updates? Is there some documentation I missed?