-
Notifications
You must be signed in to change notification settings - Fork 773
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
clobber for directories #201
Comments
This feels like maybe it'd be doing too much though. Copying shouldn't read the destination unless there is a conflict with what is being copied, right? Maybe a better solution would be that if a destination directory exists, an event is emitted allow the user to read the directory and then take action. IDK. |
Why no both? :-) If a conflict on destination arises, call a {
onConflictDir: 'merge',
onConflictFile: 'overwrite'
} Nice, eh? :-) |
It's not a bad idea, but my priority is to get to 1.0 first. We can then revisit it then :) Tagged as |
I agree :-) |
Reading the code I've found
copy
(andmove
) merge the content of the directories if the destination (and any of its subfolders) exists. That's just the feature I was looking for :-D But I've noticed that there's no option to delete destination (sub-)folders to only have the files we are copying and none of the old ones, the same way theclobber
option overwrite destination files when enabled...The text was updated successfully, but these errors were encountered: