Repository navigation
fix(pairwise): make it recursion-proof - #4743
Merged
Merged
Conversation
Pull Request Test Coverage Report for Build 8430
💛 - Coveralls |
cartant
reviewed
Apr 27, 2019
thorn0
changed the title
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Description:
pairwisecallsnextbefore saving the current value as the previous one, which makes it not recursively re-enterable. If its subscriber synchronously triggers the input observable,pairwiseerroneously emits a pair with the wrong previous value.Related issue: reduxjs/redux#3404