Releases: tomwanzek/d3-v4-definitelytyped
v1.15.0
v1.14.0
v1.13.0
Additional completed modules with this release:
- d3-collection
Changes/fixes to modules previously released as complete:
- closed open issue related to d3-zoom
ZoomBehavior
. DOM element and Datum type for selection/transition to which.transform(...)
,.translateBy(...)
,.scaleBy(...)
and.scaleTo(...)
can be applied are again restricted to the same types as those underlying theZoomBehavior
overall. - Updated d3-brush, d3-drag and d3-zoom to consistently use
ArrayLike
instead of the too restrictiveNodeListOf
as an alternative to a properArray
.
v1.12.1
With respect to the d3-modules previously completed as per the documented release notes, the following modules were updated:
- d3-selection
- d3-transition
The changes add additional flexibility with respect to the now closed BaseType issue
v1.12.0
v1.11.0
v1.10.0
v1.9.0
v1.8.0
This is a pre-release to mark the completion of additional definitions with supporting tests for the following D3 version 4 modules (in alphabetical order):
- d3-axis
- d3-time-format
- d3-shape
Furthermore, a minor change was made to the Selection
and Transition
interfaces in modules d3-selection and d3-transition, respectively. The methods attr(...)
, style(...)
and text(...)
no longer allow a general object which can be implicitly coerced to 'string'. Where a value is used for setting, they accept primitives string | number | boolean
. All other objects with a toString()
method must be explicitly converted using such a method, where required.
This change was made, to improve type safety, when passing e. g. arc
and symbol
generators from d3-shape into the attr(...)
method as a callback.