Robotframework-lsp do not find keywords imported relatively

cc. @fabioz @avaissi @orlof

I have xeus-robot and robotframework-lsp installed in my environement. I have a keywords.robot file containing:

*** Settings ***
Library  String

*** Keywords ***
This Is A Dummy KeyWord
    Convert To Lower Case  "HELLO"

And a Notebook running xeus-robot next to it:

The problem is that it doesn’t find the keywords defined in keywords.robot that is imported relatively.

Although we saw that there was a .virtual_documents directory created, that seem to contain files that were opened from JupyterLab and that are used by jupyterlab-lsp. It seems that once keywords.robot is added to this .virtual_documents directory it works and the keywords are found properly.

I cannot seem to be able to reproduce the issue in Python (having a local python module next to a Notebook), is there something special that python-language-server does?

[fabioz]

Now seeing https://github.com/krassowski/jupyterlab-lsp/issues/537, it seems that’s the same request as this…

[fabioz]

I think the main issue is that you’re seeing the use-case where the .robot is embedded in a notebook (where the notebook is usually standalone and thus the uri in the .virtual_documents may make sense) vs. a case where the user opens a .robot file directly, where the original uri should be kept.

Although even in the case where it’s in a notebook, a concrete file in the .virtual_documents may not really be needed (just keeping the contents in memory and passing the original uri postfixed by .robot may be better as the language server can then search for other – actual .robot files in the filesystem).

It’s then the job of the language server to actually know how to work with partial contents in-memory or in-disk.