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

Clone the original file prior to renaming #56

Merged
merged 2 commits into from
Oct 6, 2015

Conversation

Josiah
Copy link
Contributor

@Josiah Josiah commented Aug 25, 2015

The file object is being mutated it should be cloned prior to the rename operation. Otherwise if there are other pipelines modifying the same file the clone could be applied twice.

This makes the results of the rename immutable.

Because the file object is being mutated it should be cloned prior to the rename
operation.
@shinnn
Copy link
Collaborator

shinnn commented Aug 25, 2015

@Josiah Can you add a test that fails without this change?

@Josiah
Copy link
Contributor Author

Josiah commented Aug 25, 2015

@shinnn I've added a failing test

This covers the basic scenario in which I was experiencing this bug.

@yocontra
Copy link
Collaborator

+1 - this should have been happening

@yocontra
Copy link
Collaborator

yocontra commented Oct 6, 2015

Oh, I forgot I can merge this. Thanks!

yocontra pushed a commit that referenced this pull request Oct 6, 2015
Clone the original file prior to renaming
@yocontra yocontra merged commit 17d44ec into hparra:master Oct 6, 2015
@EmielM
Copy link

EmielM commented Nov 6, 2016

Could you publish this change to npm also? Lack of it introduces some very hard to debug problems!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants