Mike Bostock
Mike Bostock
Should _hexbin_.hexagon implement the [symbol type interface](https://github.com/d3/d3-shape#custom-symbol-types)? But it has a specific radius, not an arbitrary size… Should the hexagon method take a context? But then you have to construct...
It might be nice to re-design this API more along the lines of [d3-quadtree](https://github.com/d3/d3-quadtree) so that points could be incrementally added and removed from the bins, rather than requiring all...
The _node_.id property is set by d3-stratify, but it isn’t an “official” part of the _node_ interface, and so it’s not copied by _node_.copy. It’d be nice if it were.
Currently, you have to do some tedious dancing to change the orientation of d3.cluster, d3.tree or d3.partition, for example swapping _x_ ↔︎ _y_ and _width_ ↔︎ _height_. It’d be nice...
Most of them support _layout_.size, but we should also support _layout_.extent for more control. - [ ] cluster.extent - [ ] tree.extent - [ ] treemap.extent - [ ] partition.extent...
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...
Would it be possible to generalize the stable update of an existing treemap? Currently the squarify layout stores its arrangement in _node_._squarify, but it seems like it should be possible...
Per https://github.com/d3/d3-interpolate/issues/64#issuecomment-499141634. Though, the difference between this as d3.interpolateRgb.gamma(2.4) is pretty minor.
I’d like a version of d3.interpolateTransform that, instead of taking a transform string as d3.interpolateTransformCss and d3.interpolateTransformSvg do, takes an array of six numbers [*a*, *b*, *c*, *d*, *tx*, *ty*]...
The following input results in a blank canvas: ``` 100,100 200,200.0001 300,300 ```  However, note that three exactly collinear points produce the...