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

[BREAKING] copy & copySync: do not overwrite src & dest paths to avoid side effects #554

Merged
merged 1 commit into from Apr 6, 2018

Conversation

manidlou
Copy link
Collaborator

@manidlou manidlou commented Mar 2, 2018

Overwriting src and dest paths with their resolved ones would result in some side effects like #552. This is a fix to avoid that.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.06%) to 85.442% when pulling 7262447 on fix-copy into a0d44c1 on master.

@RyanZim
Copy link
Collaborator

RyanZim commented Mar 2, 2018

@manidlou wouldn't this be technically a breaking change?

Copy link
Collaborator

@RyanZim RyanZim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM

@manidlou
Copy link
Collaborator Author

manidlou commented Mar 3, 2018

wouldn't this be technically a breaking change?

@RyanZim that's right.

@manidlou manidlou changed the title copy & copySync: do not overwrite src & dest paths to avoid side effects [BREAKING] copy & copySync: do not overwrite src & dest paths to avoid side effects Mar 3, 2018
@RyanZim RyanZim added this to the 6.0.0 milestone Mar 15, 2018
@RyanZim RyanZim changed the base branch from master to v6-dev April 6, 2018 15:29
@RyanZim RyanZim merged commit 50c098e into v6-dev Apr 6, 2018
@RyanZim RyanZim deleted the fix-copy branch April 6, 2018 15:31
facebook-github-bot pushed a commit to facebook/flipper that referenced this pull request Nov 14, 2018
Summary:
Changes are mostly bug fixes, that shouldn't affect us. From the change log:

7.0.1 / 2018-11-07
------------------

- Fix `removeSync()` on Windows, in some cases, it would error out with `ENOTEMPTY` ([#646](jprichardson/node-fs-extra#646))
- Document `mode` option for `ensureDir*()` ([#587](jprichardson/node-fs-extra#587))
- Don't include documentation files in npm package tarball ([#642](jprichardson/node-fs-extra#642), [#643](jprichardson/node-fs-extra#643))

7.0.0 / 2018-07-16
------------------

- **BREAKING:** Refine `copy*()` handling of symlinks to properly detect symlinks that point to the same file. ([#582](jprichardson/node-fs-extra#582))
- Fix bug with copying write-protected directories ([#600](jprichardson/node-fs-extra#600))
- Universalify `fs.lchmod()` ([#596](jprichardson/node-fs-extra#596))
- Add `engines` field to `package.json` ([#580](jprichardson/node-fs-extra#580))

6.0.1 / 2018-05-09
------------------

- Fix `fs.promises` `ExperimentalWarning` on Node v10.1.0 ([#578](jprichardson/node-fs-extra#578))

6.0.0 / 2018-05-01
------------------

- Drop support for Node.js versions 4, 5, & 7 ([#564](jprichardson/node-fs-extra#564))
- Rewrite `move` to use `fs.rename` where possible ([#549](jprichardson/node-fs-extra#549))
- Don't convert relative paths to absolute paths for `filter` ([#554](jprichardson/node-fs-extra#554))
- `copy*`'s behavior when `preserveTimestamps` is `false` has been OS-dependent since 5.0.0, but that's now explicitly noted in the docs ([#563](jprichardson/node-fs-extra#563))
- Fix subdirectory detection for `copy*` & `move*` ([#541](jprichardson/node-fs-extra#541))
- Handle case-insensitive paths correctly in `copy*` ([#568](jprichardson/node-fs-extra#568))

Reviewed By: jknoxville

Differential Revision: D13023753

fbshipit-source-id: 1ecc6f40be4c8146f92dd29ede846b5ab56765ea
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants