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.

Sign up for GitHub

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

Jump to bottom

setState in Lifecycle #4

Open
Siubaak opened this issue Apr 4, 2018 · 2 comments
Open

setState in Lifecycle #4

Siubaak opened this issue Apr 4, 2018 · 2 comments
Assignees
@Siubaak
Labels
bug Something isn't working
Milestone
0.3.0

Comments

@Siubaak
Copy link
Owner

Siubaak commented Apr 4, 2018

Make the behavior of setState clear in the lifecycle methods, to avoid some problem like recursive update.
@Siubaak Siubaak self-assigned this Apr 4, 2018
@Siubaak Siubaak added the bug Something isn't working label Apr 4, 2018
@Siubaak Siubaak modified the milestones: 0.2.1, 0.3.0 Apr 4, 2018
@Siubaak
Copy link
Owner Author

Siubaak commented Apr 6, 2018

Fix this after modifying the lifecycle methods

@Siubaak
Copy link
Owner Author

Siubaak commented Apr 6, 2018

It seems that, it has no problem if async-batch-update, 'cause updates of the same instance will be merged to only one update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Siubaak Siubaak

Labels
bug Something isn't working
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
1 participant
@Siubaak