You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently to avoid an important class of bug, watch notifications propagate after the state-changing procedure has returned (notifications are queued in the event loop as below).
The text was updated successfully, but these errors were encountered:
cefn
changed the title
Recommended technique when watcher needs immediate notify in the same tick?
Recommended technique for immediate notify of write?
Mar 19, 2023
Currently to avoid an important class of bug, watch notifications propagate after the state-changing procedure has returned (notifications are queued in the event loop as below).
lauf/modules/store/src/core/watchable.ts
Line 11 in 67f47c4
Can we recommend a pattern where another reference needs to track state directly (and should be updated in write).
Related the microtask should perhaps not be inline in notify, since partitioned stores may end up with two event loop ticks for no reason.
lauf/modules/store/src/core/partition.ts
Lines 31 to 38 in 67f47c4
The text was updated successfully, but these errors were encountered: