fix resource state

[mdynnl]

fixes #1309

[coveralls]

Pull Request Test Coverage Report for Build 3341902142

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 89.089%

---

Totals
Change from base Build 3287627654:	0.0%
Covered Lines:	1276
Relevant Lines:	1362

---

💛 - Coveralls

[ryansolid]

Looking at the fix I'm worried something more serious is going on. These are in a runUpdate batch so they should run together and the order not matter. @mdynnl can you speak to this at all?

[mdynnl]

The write order actually affects the order updates run. It wouldn't matter if res is accessed before state (res.loading) in the same computation stopping further execution. But if state also has other computations that doesn't depend on res, this would allow them to run first. (Edit: I'm not entirely sure if this should be allowed)

Also, onError can be used if this is desired. ErrorBoundary would also work but res.loading has to be read outside of it.