Uh oh!
There was an error while loading. Please reload this page.
Solution for shouldComponentUpdate issue - #15
Merged
mzabriskie merged 1 commit intoNov 5, 2015
Conversation
mzabriskie added a commit
that referenced
this pull request
Nov 5, 2015
[fixed] shouldComponentUpdate issue
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Solution for issue #13
Simply does cloning of
configobject before passing it to_initmethod to prevent mutation of original config prop and therefore makes fair comparison possible between previous and next state of config object passed via props.