mirror of https://github.com/sveltejs/svelte
chore: deactivate batch after async derived resolves (#17865)
Extracted from #17805. Similar to #17864, I'm not aware of any bugs resulting from this, but the fact that we're setting `current_batch` before calling `internal_set` and then not _unsetting_ `current_batch` feels like something that could potentially bite us.pull/17873/head
parent
2a1f5ada13
commit
3df2645451
Loading…
Reference in new issue