-
Notifications
You must be signed in to change notification settings - Fork 93
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
Support case where default value for an env var is a variable. #715
Labels
Comments
Thx for reporting it! Also the same problem is reproduced with this plain default construct as well: Resource %{RESOURCES_ENV=resources}/common.resource so I guess it has to do with env vars in general that have defaults. Also on my Mac it doesn't recognise the path given this construct: *** Settings ***
Resource ${RESOURCES}/common.resource
*** Variables ***
${RESOURCES} %{HOME}/Resources and it stays red-highlighted and go-to-definition doesn't work. (while the robot runs perfectly fine and the env var is defined in the system)
|
fabioz
added a commit
that referenced
this issue
Aug 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: