Open 0Hughman0 opened 3 months ago
Ah so I think this exists because resolve()
is the only method that gets ride of relative paths e.g. ../above
.
Is there a reason we're concerned about this? Are there tests that fail for this?
A workaround is just setting the project_folder
value after init.
This line
Means if the project_folder is set to a symlink, this gets undone upon initialisation, which seems to cause problems generating relative paths because drives are different
Might be better to change to
path.absolute()
, although not sure if there was a good reason to useresolve()
in the first place.dirty workaround is: