-
Notifications
You must be signed in to change notification settings - Fork 587
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
Don't synchronously unmount components after -updateState #87
Labels
Comments
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 23, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 23, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 23, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 27, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 27, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
Apr 29, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
adamjernst
added a commit
to adamjernst/componentkit
that referenced
this issue
May 4, 2015
This work is aimed at creating a new data source to replace the current implementation. The goals are: - Fix the race conditions described in facebook#15 - Enable batching state updates to the end of the run loop as described in facebook#87 - Enable asynchronous state updates in a less hacky way - Allow all operations on a data source to be performed synchronously or asynchronously in a safe manner (right now, insertions are always async) These objects are merely immutable value objects or announcers, not the actual data source implementation. That will come later.
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed. |
This is fixed with the transactional data source! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CKComponentActionSend
can crash if called afterupdateState
because updating state may unmount the component synchronously.See: #86
@adamjernst says:
The text was updated successfully, but these errors were encountered: