Repository navigation
batch invalidations - #204
Merged
Merged
Conversation
|
Size Change: +40 B (+1.16%) Total Size: 3.48 kB
ℹ️ View Unchanged
|
tombl
force-pushed
the
push-wrnolppoputo
branch
5 times, most recently
from
October 29, 2025 14:22
1b25ee7 to
cd2298a
Compare
tombl
force-pushed
the
push-wrnolppoputo
branch
from
February 1, 2026 07:45
cd2298a to
b621881
Compare
batching makes things like 10x faster anyway. at least returning a promise makes it easy to do things after the update.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
...in a microtask.
makes
invalidateasync, so while it's less convenient, you can stillawaitor.thenfor your post-update DOM handling needs.good for perf but mainly because I've just discovered a pile of reentrancy issues and don't want to keep hunting for them individually.
note that most usages in the examples didn't even need updating because very few actually need this. this does probably break all the benchmarks though.
closes #200