Replace runWithTransactions to flushCallbacks finalizer for Improved Flow Control and Compatibility #2946
+65
−48
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.
Summary
Current implementation with
runWithTransactions
uses a single synchronous callback (fn
) invocation followed by conditionally running store hooks. For some flows, this code reduces to simply callingfn
. The states in which hooks should be called are well defined so refactoring to synchronously calling a finalizer (flushCallbacks
) is introduced in this PR.A side-effect of this PR is it resolves several incompatibilities with jotai-effect.
Details
flushCallbacks
is called at the end of 7 flows:Check List
pnpm run fix:format
for formatting code and docs