-
Notifications
You must be signed in to change notification settings - Fork 772
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
Rewrite copySync #519
Rewrite copySync #519
Conversation
IDK! it is so strange! the unit test for the case when |
Any ideas? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Will look at timestamps later. |
@manidlou Spent a bunch of time messing with this, can't figure it out. I'm gonna say just put a conditional in place that that flaky test gets skipped on older node versions. @jprichardson Let me know if you disagree here. |
I agree. I played with it too, but no success! I am not sure but it seems like it is somehow related to node internals. |
If looks good, I will squash this. |
@jprichardson do you have any concerns regarding this? |
Nice work @manidlou! |
This is the rewrite of
copySync
to matchcopy
. It should resolve #83, #198, and #464. Added corresponding tests for those issues. Also, removed thefixtures
folder that was used by thecopy-sync-preserve-time.test.js
, instead the fixtures directory is created in the code.Please let me know if anything doesn't look alright!