Closed rjrjr closed 7 years ago
Note that exposing HistoryUpdater.DoSet
is very intentional. I have had to replicate that in app code more than once, can't imagine I'm the only one.
I like this alot.
Offline discussion w/@loganj, we're reluctant to open this up hook without thinking about it a bit more. Is the queue really something we should be exposing even more like this, or would that get in the way of a longer term vision that eliminates the need for it?
In response to the discussion in #197. Allows app code to mutate the history safely despite the raciness of asynchronous transitions.