You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that with the latest update the files are not being put where they should be.
I'm on mac.
I have relative destination paths like destination/${file_path}, so for example destination/project/source/folder/file/number.one. With the version 1.0.0 it works fine.
With the version 1.0.1 the files are being put to destination/User/username/a/long/path/to/my/project/source/folder/file/number.one.
The rename function gets the fullPath as an absolute system path now, as opposed to the project relative path.
So /Users/username/long/path/to/project/folder/file/path instead of folder/file/path;
Should I update some params for this to properly use relative paths again?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I noticed that with the latest update the files are not being put where they should be.
I'm on mac.
I have relative destination paths like
destination/${file_path}
, so for exampledestination/project/source/folder/file/number.one
. With the version1.0.0
it works fine.With the version
1.0.1
the files are being put todestination/User/username/a/long/path/to/my/project/source/folder/file/number.one
.The
rename
function gets thefullPath
as an absolute system path now, as opposed to the project relative path.So
/Users/username/long/path/to/project/folder/file/path
instead offolder/file/path
;Should I update some params for this to properly use relative paths again?
Beta Was this translation helpful? Give feedback.
All reactions