-
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 copy #502
Rewrite copy #502
Conversation
Aah! I forgot node 4 cannot read new es |
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.
Code LGTM.
Briefly reviewed tests; your test descriptions look like you're testing all the right cases. Did not line-by-line review all the actual test code to ensure the tests actually assert the behavior described.
Would like at least quick review from @jprichardson as well.
@manidlou Not sure why this is WIP? We should probably merge this into a |
Yeah, primarily because of
Good idea! 👍 |
Stellar work @manidlou! Please squash the changes to account for the destructuring fix, and then it LGTM. |
Sure thing. |
d9d0e74
to
fe0bfe2
Compare
Squash done! 😃 |
Will merge when I’m on desktop. |
@RyanZim ping?! |
Thanks for the ping @manidlou, I totally forgot this. Merged to new |
Started #374.
Fixes #83 and #198.
This implementation uses
recursive
pattern for copying directories.recursive
pattern has shown better performance thanPromise
(copy-benchmark). If this looks good, then we will applyfs.copyFile()
to it.Any feedback appreciated! 😄