-
Notifications
You must be signed in to change notification settings - Fork 24
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
Handle concurrent state updates #268
Comments
This issue results into numerous bugs, mainly connected to keeping controlled inputs in a form. This needs to be resolved. I will try to think of a possible solutions and pick the best at the moment. |
I've summed it up in one of the pull requests, but I am going to repeat this here too:
|
What
I propose to provide a consistent reliable way of handling concurrent state updates.
Why
At the moment some concurrent updates result into obsolete
fields
. That causes various unexpected behaviors.How
fieldChange
during a certain period of time and handle all the accumulated payload at once. Con: That would mean an idle accumulation period, and "synced" patch state update.fields
reference onform.handleChange
. In other words, maybe add a second parameter toform.updateFieldsWith(fieldProps, fields)
to have explicitfields
passed.The text was updated successfully, but these errors were encountered: