Description
Describe the bug
when I use --no-vcs and --root on a project with submodules I have to set absolute paths in robot.toml for the python-paths otherwise the test resources cannot be found
Steps To Reproduce
Steps to reproduce the behavior:
using a dev container. folder structure us like this:
/workspaces/project-title/src/test_framework/robot.toml
normally I have to have the robot.toml at the project-title level but this is not ideal as the test_framework repo may be used on other projects which have somilar code base so we can recycle resources.
I have these env variables set:
ROBOTCODE_NO_VCS=true
ROBOTCODE_ROOT=/workspaces/project-title/src/test_framework/
in robot.toml I can use relative (to the ROBOTCODE_ROOT env var) paths for output-dir, paths and variables which are paths but I can only use absolute paths for the python-path.
Expected behavior
I should be able to use relative (to the ROBOTCODE_ROOT env var) python-path entrys so this can be used in a CI pipeline etc...
Screenshots/ Videos
If applicable, add screenshots or videos to help explain your problem.
Desktop (please complete the following information):
- VS Code Version [e.g. 1.95.3]
- RobotCode Version [e.g. 0.99]
- OS: Linux
- Python 3.10.12
- RobotFramework Version 7.1.1