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
It seems like considering the application, an option to protect the original filename would be valuable. At this point, I don't see a way to copy the file to another folder and rename it, but leave the original file alone.
Using %(original filename)s I was able to move the file to the new destination with the original filename, but it renamed the file in the original destination. Is there a way to reverse this in the JSON file?
The text was updated successfully, but these errors were encountered:
The current code is a bit crappy in this respect, because I added the file-moving as an afterthought - it really needs refactored..
It should parse the file, calculate the new filepath, then either rename, move or copy the file to the new path. Currently it just renames, then moves, in two largely unrelated chunks of code
It seems like considering the application, an option to protect the original filename would be valuable. At this point, I don't see a way to copy the file to another folder and rename it, but leave the original file alone.
Using %(original filename)s I was able to move the file to the new destination with the original filename, but it renamed the file in the original destination. Is there a way to reverse this in the JSON file?
The text was updated successfully, but these errors were encountered: