I tried my best but failed miserably to find any logic behind the given merged data trees. Why do we have 1, then A, B, C, then 2 and 3 at the end?
I thought that D1, “A” should be the first in the list, but apparently not. What am I missing here? I guess it has something to do with the path names, but still…
p.s. I can clearly see the logic if I simplify both D1 and D2 data trees.
Thanks for the fast reply as usual @Joseph_Oster, but why do we have A, then 1, 2, 3, followed by 2 and 3? I mean, what´s the logic to generate that specific data structure?
Merge component merges data depending on the path of each branch and the order that data is connected to its inputs, so it’s important for it to be “sensible enough” to distinguish from {0} and {0;0} and {0,0,0}
generally speaking, for the GH components, it’s more in the direction of list matching, so for instance Concatenate will produce the wanted result despite the paths being different, because it’s 3 lists Vs 3 lists: