Update index.js#939
Merged
Merged
Conversation
Solves the issue of state messing up when parent component calls setState [ref leecade#569]
cchawn
added a commit
to wealthsimple/react-native-swiper
that referenced
this pull request
Mar 19, 2019
Contributor
|
This repo dead: #713 |
This was referenced Jun 26, 2019
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Solves the issue of state messing up when parent component calls setState [ref https://github.com//issues/569]
[ref https://github.com//issues/938]
Is it a bugfix ?
Is it a new feature ?
Describe what you've done:
Whenever parent component makes any change to state, ComponentWillReceiveProps is called (not sure why) but it messes the state. I referred to this fix from 529 itself and found that it solves several other similar reported issues. All that's done is to avoid calling state change in this event.
How to test it ?
[ref https://github.com//issues/938]