6.0

[mbostock]

d3-array

• Add d3.group.
• Add d3.groups.
• Add d3.rollup.
• Add d3.rollups.
• Add d3.bin.
• Add d3.count. Thanks, @Fil!
• Add d3.least.
• Add d3.leastIndex.
• Add d3.maxIndex.
• Add d3.minIndex.
• Add d3.quickselect.
• Rewrite d3.median to use quickselect.
• Allow more than two iterables for d3.cross.
• Deprecate d3.scan; use d3.leastIndex instead.
• Deprecate d3.histogram; use d3.bin instead.

d3-collection [Removed!]

• Remove d3.keys; use Object.keys.
• Remove d3.values; use Object.values.
• Remove d3.entries; use Object.entries.
• Remove d3.map; use Map.
• Remove d3.set; use Set.
• Remove d3.nest; use d3.group, d3.rollup, etc.

d3-delaunay [Added!]

• Add d3.Delaunay.

d3-force

• Add support for iterables.

d3-hierarchy

• Add node.find.
• Add node[Symbol.iterator].
• Add support for iterables.
• Pass index to node.each and other traversal methods.

d3-random

• Add d3.randomInt.
• Add d3.randomBinomial.
• Add d3.randomGeometric.
• Add d3.randomPareto.
• Add d3.randomBernoulli.
• Don’t wrap Math.random in the default source.

d3-shape

• Add support for iterables.

d3-scale

• Add support for iterables.
• …

d3-selection

• Change selection.on to pass the event.
• Remove d3.event!

d3-transition

• Change d3-selection to be a peer dependency.

d3-voronoi [Removed!]

• Remove d3.voronoi; use d3.Delaunay.

Upgrade:

• d3-array
• d3-axis
• d3-brush
• d3-chord
• d3-color
• d3-contour
• d3-dispatch
• d3-drag
• d3-dsv
• d3-ease
• d3-fetch
• d3-force
• d3-format
• d3-geo
• d3-hierarchy
• d3-interpolate
• d3-path
• d3-polygon
• d3-quadtree
• d3-random
• d3-scale
• d3-scale-chromatic
• d3-selection
• d3-shape
• d3-time
• d3-time-format
• d3-timer
• d3-transition
• d3-zoom

[mbostock]

I’m thinking maybe we don’t need to do a major version bump across all the modules just for the sake of announcing ES2015 syntax adoption. We could bump those modules as necessary when we make changes that benefit from ES2015 syntax, and then the d3 package could use a version range (e.g., 1.1.0 - 2).

But any module that depends on a module with a new major version bump will also need a major version bump. For example, even if d3-brush doesn’t need ES2015 syntax yet, we’ll want it to be compatible with d3-selection@2, which will mean d3-brush needs a major bump. So most packages might need a major bump anyway.

[curran]

Really looking forward to 6.0!

[curran]

I'd be interested in trying out a pre-release of 6.0, similar to the 5.0 prerelease.

Might this be in the realm of possibility? Anyone else interested?

Also noticed that d3-array quantileSorted is done and can be checked off.

[gordonwoodhull]

We at dc.js are planning to switch to the individual D3 modules in order to test against 6.0 before it’s released. But I agree, a release candidate would give us more certainty that we’re testing the right thing.

For us, the d3-selection changes may have the biggest impact - iterators etc. I don’t think those changes have started yet.

[mbostock]

There’s a two branch in d3-selection and d3-transition, but the removal of d3.event hasn’t been implemented yet which is blocking the release of those modules.

[mbostock]

d3.event removal has been implemented, and 2.0.0-rc.1 releases for d3-selection and d3-transition if you want to try them out!

It looks like the major thing blocking this release is now just the adoption of iterables in d3-hierarchy and d3-shape. A major part of this release is the adoption of new ES language features including iterables, so d3-hierarchy and d3-shape should be upgraded before we release. The other relevant modules (d3-array, d3-selection and d3-scale) have already been upgraded.

[mbostock]

I’ve implemented iterables for d3-hierarchy and d3-shape, so major releases of those modules should be imminent. Edit: Oops, I haven’t done d3-shape yet.

The last remaining step is to upgrade d3-brush, d3-drag and d3-zoom to the d3-selection changes, and specifically the removal of d3.event, d3.customEvent etc.

[Fil]

d3-hexbin has PR d3/d3-hexbin#19 that does:

• canvas support
• incremental binning (add and remove points)
• hexgrid rotation and translation
• finding the bin from coordinates without adding the point
• accepts iterables

[mbostock]

I think I want to give d3-hexbin a little more time to “bake” and we should consider deferring its addition to 6.1. I haven’t had a chance to review the proposed API changes yet. There is other blocking work for 6.0 that needs to be done first, as well, notably upgrading d3-brush, d3-drag and d3-zoom to d3-selection 2.0 (namely the removal of d3.event and related changes).

[jipexu]

HI great work
this 6 version will have heavy breaking change ?
(little bit worry to change a lot of code ...)

[Fil]

https://github.com/d3/d3/releases/tag/v6.0.0