Keywords not imported correctly when resource path contains ${CURDIR}

[wwuoti]

When specifying a resource with a path containing CURDIR, the path to the resource is not resolved.

Consider the following example:

curdir_import_test.zip

curdir_import_test
|--resource_folder
|   |--resource1.robot
|--test_importing_from_curdir.robot

resource1.robot:

*** Keywords ***
Keyword In Resource File
    Log To Console    Test keyword in resource file

But when the resource is imported in test-importing_form_curdir.robot

Removing ${CURDIR} from the file path fixes this issue:

[fabioz]

Actually, reopening, I had misunderstood CURDIR... it maps the current directory of the .robot or .resource, thus, the language server should support it.

As a note, I don't really see any reason to use CURDIR at that context (since you can just make the path relative), but the language server should support it anyways.

[ORicardoSouza]

@wwuoti
seems to be ok, just merge?

[arnewohletz]

I had a similar issue and resolved it by specifying a custom variable in my project's settings.json (here on Windows):

{
  "robot.variables": {
		  "RESOURCES":"C:\\my_project\\Resources",
	  }
}

Reference: Configuration setting

Then using it like this:

*** Settings ***
Resource      ${RESOURCES}/my_resource.robot

Naturally for Robot Framework, I needed to define the same variable (e.g. in a variable file) and pass it as parameter (using either --variable or --variablefile) to my robot test runs.