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
This will be a breaking change, but I think we really want hierarchy layouts to be immutable—to return a copy of the hierarchy with the layout’s computed coordinates applied, rather than setting the computed coordinates directly on the input hierarchy. Given that the semantics of node.copy are already defined, this should not be difficult to do. It shouldn’t be hard to implement resquarify, since it can read the input node._squarify and set the output node._squarify.
Probably this means that node.sum and node.sort should return copies of the hierarchy, too, making everything immutable.
The text was updated successfully, but these errors were encountered:
This will be a breaking change, but I think we really want hierarchy layouts to be immutable—to return a copy of the hierarchy with the layout’s computed coordinates applied, rather than setting the computed coordinates directly on the input hierarchy. Given that the semantics of node.copy are already defined, this should not be difficult to do. It shouldn’t be hard to implement resquarify, since it can read the input node._squarify and set the output node._squarify.
Probably this means that node.sum and node.sort should return copies of the hierarchy, too, making everything immutable.
The text was updated successfully, but these errors were encountered: