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
I wonder if it should not be an option of stratify (or even the default, if the current behavior is considered a bug), to create a leaf node to represent the data of a node that has children.
with the typical value:
/gallery,4
/gallery/chart-a,2
/gallery/chart-b,1
currently stratify builds a tree with three nodes and the values:
/gallery 4
/gallery/chart-a 2
/gallery/chart-b 1
and a treemap representation (for example) doesn't see the value of 4 that pertains to the /gallery node.
With the following function, we would introduce a child node /gallery/ with that value:
I wonder if it should not be an option of stratify (or even the default, if the current behavior is considered a bug), to create a leaf node to represent the data of a node that has children.
with the typical value:
currently stratify builds a tree with three nodes and the values:
and a treemap representation (for example) doesn't see the value of 4 that pertains to the /gallery node.
With the following function, we would introduce a child node /gallery/ with that value:
see https://observablehq.com/@d3/treemap-parent-with-value-206
The text was updated successfully, but these errors were encountered: