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
Right now we render the hierarchy once for assignments, and that hierarchy is then like it is a static one.
But I think we want each node to have its own, possibly different hierarchy, because when we look at ancestors and descendants, we care about that source at that node. I.e. if I have a change for a source above that node, it should apply, regardless of if it would be in the target's hierarchy.
The text was updated successfully, but these errors were encountered:
...I think.
Right now we render the hierarchy once for assignments, and that hierarchy is then like it is a static one.
But I think we want each node to have its own, possibly different hierarchy, because when we look at ancestors and descendants, we care about that source at that node. I.e. if I have a change for a source above that node, it should apply, regardless of if it would be in the target's hierarchy.
The text was updated successfully, but these errors were encountered: