…ation (#9556)

* Updates examples for invalidation from mutations

* ci: apply automated fixes

* Elaborate promise

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

…9c40848 (#9473)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…st' import (#9569)

Co-authored-by: Jonghyeon Ko <manudeli.ko@gmail.com>

…rs (#9593)

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

…tra parentheses) (#9596)

Co-authored-by: Jonghyeon Ko <manudeli.ko@gmail.com>

Co-authored-by: Jonghyeon Ko <manudeli.ko@gmail.com>

Co-authored-by: Jonghyeon Ko <manudeli.ko@gmail.com>

the switch from the callback approach to async/await with catch was necessary to be able to transform errors into revert-state data for imperative query calls; however, this was a change in behavior because catch in async/await doesn't happen immediately - it runs in the next microtask. That opened up an opportunity for a slight race condition if we re-start a fetch in-between. And who does that? Of course, React Strict Mode.

This PR moves the actual state reverting back to a callback (so it happens synchronously), while still keeping the try/catch refactoring merely to transform the promise and the usual error handling