Hi, I am trying to understand a strange bug in my application. I am rendering a tree of components and the application allows to add or remove nodes. In db, each node has a unique id and I have them stored as map from ids to a map describing the node (and its children, etc.). Rendering just recursively displays the nodes. When I load the application and remove a node, the subscription for its parent is modified and the component of the node is not rendered correctly. But when I load the application, add a node and then remove the node, it will call rendering of the removed node (whose subscription returns nil), which throws an error. Basically what happens that both subscriptions for the node and its parent are updated, but due to some ordering first the node is rerendered (which throws an error) and then its parent would be rerendered, which would actually remove the node. Is there a way how I can specify/control the order in which the components are rerendered when their subscriptions change?

how come https://github.com/day8/re-frame/tree/master/examples/todomvc isn't actually in http://todomvc.com/?

was a bit surprised by that, the reagent one is

I suppose it might because of the disclaimer?

> But this is NOT your normal, lean and minimal todomvc implementation, geared towards showing how easily re-frame can implement the challenge.