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

Update index.js #939

Merged
merged 2 commits into from
Jun 26, 2019
Merged

Update index.js #939

merged 2 commits into from
Jun 26, 2019

Conversation

deepakaggarwal7
Copy link
Contributor

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 ?

  • No

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]

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
@retyui
Copy link
Contributor

retyui commented Mar 25, 2019

This repo dead: #713

@ArrayZoneYour ArrayZoneYour merged commit c99f80a into leecade:master Jun 26, 2019
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.

Unable to change number of screens dynamically
3 participants