apply scheduled patches only once #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yep, I forget about 5.3, I'l soon fix |
antecedent
added a commit
that referenced
this pull request
Mar 18, 2015
apply scheduled patches only once
|
Thank you for taking the time to isolate the problem in Patchwork's code :) Merged, finalized, will soon tag as 1.3.4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our project we use zend autoloader, so it's not easy control then class will be loaded, before or after I replace it's method. I found that if class loaded after, sometimes my replacement function call multiply time per one original method call.
That look like it's right to unset State::$scheduledPatches after them applied, but I'm not sure.