Fix concurrency issues in effectful form combinators #29
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.
asyncEffect
andeffect
are used for effectful updates in specific parts of form data based on other parts of it. The old formulation of these combinators led to concurrency issues whenever two async updates would occur simultaneously based on a previous version of the form data (captured in a closure withwithValue
).This pull request fixes this problem by enabling concurrency in
asyncEffect
and its derived combinators.This is a breaking change.