Steps to Reproduce:
Repeating the above steps with the file named "testfile.txt", the overwrite actually occurs.
I am using the fileService.copy
I could pass the overwrite flag but that is not what I want. I would expect the fileService to find a new name and copy without overwriting.
@isidorn
I would expect the fileService to find a new name and copy without overwriting.
The file service is not the right place for that, it takes a path and does something with it, but will not start to come up with new file names if there is a conflict. You will have to come up with a filename from the outside if there is a conflict.
Think about the file service like node.js FS API. It is pretty much that.
Ok, so the download would have to do something similar to the copy.
Would have to check if there are overwrites and come up with a new name.
Marking as a feature request for now and we can tackle in the future.
Same problem here but occurs with file extension. Tried it on multiple files and filetypes.
VSCode 1.40.2
Same here. I was attempting to download a local copy of a build artifact through SSH remote, and couldn't understand my results at all until I realised that the file transfer was refusing to overwrite despite the dialog which asked me to confirm that I want to overwrite.
Thanks for the fix :) looking forward to the release.