svelte

Commit Graph

Author	SHA1	Message	Date
Simon H	bc82a55647	fix: ensure scheduled batch is flushed if not obsolete (#18131 ) The logic of checking that the current batch is still the generated one is flawed. If microtasks align the current batch can be a different value even if the batch still need to be flushed. This therefore switches the heuristic to what it actually should express: "has this batch run already?" Fixes #18126 (because the batch isn't running, it later runs into the invariant)	4 months ago

Author

SHA1

Message

Date

Simon H

bc82a55647

fix: ensure scheduled batch is flushed if not obsolete (#18131 )

The logic of checking that the current batch is still the generated one
is flawed. If microtasks align the current batch can be a different
value even if the batch still need to be flushed. This therefore
switches the heuristic to what it actually should express: "has this
batch run already?"

Fixes #18126 (because the batch isn't running, it later runs into the
invariant)

1 Commits (entangle-batches)