Skip to content
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

Reconsider export behavior when a file already exists #230

Open
manthey opened this issue Oct 14, 2021 · 0 comments
Open

Reconsider export behavior when a file already exists #230

manthey opened this issue Oct 14, 2021 · 0 comments
Labels
low Lower priority

Comments

@manthey
Copy link
Contributor

manthey commented Oct 14, 2021

Currently, when we export a file and a file of the same name already exists, we don't replace it. In the case where it has the same size, it is likely the same file and we report that it was already copied. In the case where it has a different size, we report that we couldn't copy the file (FailedToExport appears in the report). We might want to make this behavior configurable or change it, since it leads to confusion. Possible behaviors: (a) the current behavior -- leave the original file and don't copy the new file, (b) replace the original file with the new file -- possibly dangerous, but useful if there had been a partial transfer, (c) rename one of the files.

@manthey manthey added the low Lower priority label Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low Lower priority
Projects
None yet
Development

No branches or pull requests

1 participant