Skip to content
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

${EXECDIR} default value for import paths #263

Closed
zied-cision opened this issue Mar 11, 2021 · 4 comments
Closed

${EXECDIR} default value for import paths #263

zied-cision opened this issue Mar 11, 2021 · 4 comments
Labels
enhancement New feature or request robotframework-ls wontfix This will not be worked on

Comments

@zied-cision
Copy link

Is your feature request related to a problem? Please describe.
Pycharm-lsp is unable to resolve resource paths using the builtin variable ${EXECDIR}, so all keywords are not identified.

*** Settings ***
Resource          ${EXECDIR}/PageObjects/Login.resource

Describe the solution you'd like
Is it possible to consider ${EXECDIR}, as an abosolue path for the project root (same like $PROJECT_DIR$ path variable)

@zied-cision zied-cision added enhancement New feature or request robotframework-ls labels Mar 11, 2021
@zied-cision
Copy link
Author

This will help a lot, especially if you have a nested tests structure

@fabioz
Copy link
Collaborator

fabioz commented Mar 11, 2021

Seems fair... as a note, as a workaround you should be able to set robot.variables (or just Variables in Intellij) in the settings to:

{"EXECDIR": "c:/<path>"}

(until a default value is given)

@zied-cision
Copy link
Author

This workaround seems working so far.

Thanks @fabioz

@fabioz
Copy link
Collaborator

fabioz commented Oct 12, 2021

I'm closing this as won't fix.

Using ${EXECDIR} maps to the current working directory when Robot Framework is executing, so, it's possible that it points to different places and having a default is a bit odd.

You can still define the ${EXECDIR} to point to a different place using the robot.variables setting (so, the workaround is actually the official way to support it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request robotframework-ls wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants