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
As of 0.12.3, this is due how computeNodeDepths calculates depths for nodes and how computeNodeLayers depends on assumptions made in those depth calculations.
In computeNodeDepths, node depth calculations are done by traversing links. In your expected example, D is a calculated depth of 0, E of 1, F of 2 much like { A, B, C }. It doesn't have any facility for providing an override or alternate.
In computeNodeLayers, the calculation of the max number of columns is done using the max depth calculated in computeNodeDepths and is further constrained to transparently through a min of that max column count and your alignment result, resulting in an upper bound of its computed columns regardless of what you say - the exact behavior you see with Result { E, F }.
I am trying to fix the nodes' position in my sankey diagram by using a field called position.
Then I will call the nodeAlign with custom function where it return the position.
However the diagram does not render the expected result.
Please refer to the below diagram.
The text was updated successfully, but these errors were encountered: