-
Notifications
You must be signed in to change notification settings - Fork 391
fix: file#move do not delete origin file if same as destination #874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #874 +/- ##
=========================================
Coverage ? 95.29%
=========================================
Files ? 11
Lines ? 1212
Branches ? 303
=========================================
Hits ? 1155
Misses ? 29
Partials ? 28
Continue to review full report at Codecov.
|
|
Sounds like what we really should do here is to error out when the user tries to copy/move to the same destination, unless I'm missing something here? |
|
IMHO I am not sure passing same destination on copy/move deserves an error (would be a breaking change). WDYT? |
|
Yeah I would try to avoid a breaking change here as well. The draft looks good, promote it to a PR? |
4c9d057 to
7dacc3a
Compare
Currently if user passes same
bucketobject,fileobject, orfileNamestring as the original file, the client will attempt to "copy" (essentially leaving the file in place) and subsequently delete the origin/destination file.