You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a computed errors me might want to roll back the whole commit instead of just the subtree. Doing the latter is fine for now, but ultimately ends up with an inconsistent graph.
when part of the graph bails out due to an error in a computed, re-assigning the value of one of its dependencies doesn't re-run the errored computed - technically correct, since reassignment to the same value shouldn't re-run the graph
I don't think its a bug, but its something we might want to have a doc on.
The text was updated successfully, but these errors were encountered:
Found by @developit :
Test case: https://gist.github.com/developit/e9d25d6bf38dfbf1ddec13f92b4b3738
An earlier discussion:
The text was updated successfully, but these errors were encountered: