Open nruth opened 7 years ago
I haven't needed this, but if you want to build it (please include tests!), I'm welcome to a PR!
This is certainly something which I'd like to see myself. @nruth did you ever make any progress on this? My guess is that one concern might be around creating an infinite loop?
i.e. A descendant touches its parent, which touches its descendant, which touch parent etc etc...
In my given use case, I'd ideally like an object to touch all associated descendants and ancestors - how viable that is I'm not sure.
So, when a parent is updated it passes on the timestamp change to its children (descendants?).
I'd like the reverse behaviour, with an updated child passing its timestamp changes up to all of its ancestors. Something like this:
Would it make sense to support both of these in the
has_closure_tree
call?