All Versions
64
Latest Version
Avg Release Cycle
30 days
Latest Release
-

Changelog History
Page 6

  • v2.1.7 Changes

    • viewBox-based resizing of charts, by James Tindall (#1312)
    • 🔀 workaround for issue #949 merged from 2.0.4
    • ✂ remove pointless and confusing optimization from number display - it now uses computeOrderedGroups like everything else.

  • v2.1.6 Changes

    • 🛠 fix test syntax for Microsoft browsers

  • v2.1.5 Changes

    • 👀 crossfilter is loaded by its module name (crossfilter2), not its filename (crossfilter). This is intended to help webpack and other automatic module loaders. This is likely to break requireJS configurations; see #1304 for details. (#1213, #1214, #1261, #1293, #1302)
      • Default capMixin.ordering to sort decreasing by value, to emulate old group.top(N)
      • numberDisplay should pick the highest value in the case where it is given a regular group

  • v2.1.4 Changes

    • Simplified capMixin.othersGrouper default implementation by passing the rest of the items as well as those before the cap. This is possible because of #934 relying on sorting of group.all() instead of group.top(). The default implementation is now easy to understand and it should be easier to customize (if anyone should want to).
    • Added example filtering segments of stack (#657)

  • v2.1.3 Changes

    • 2.1.2 did not observe the common convention of having the rows/pie slices ordered from greatest to least - now we take from the front by default. (#1296
    • Add takeFront option, defaulted true, in case you want to take from the back isntead.
    • Remove component.json, since component-js has been deprecated for a long time (actually it got deprecated immediately after we added this in #860)

  • v2.1.2 Changes

    • Lift elasticRadius from bubbleChart to bubbleMixin, making it available to bubbleOverlay (#661) Stop using group.top() in favor of group.all() sorting and slicing. (#934)
    • Eliminate use of group.top() in cap mixin, by Macy Abbey (#1184). It already had to agree with chart.ordering() for the results to make sense.
    • Eliminate group.top() in number display. This one is more problematic but probably less common. Although the number display now defaults ordering to function (kv) { return kv.value; }, applications which use a group with multiple bins with the number display, which were using group.order() to specify which bin should be displayed, must now specify numberDisplay.ordering() instead.
    • Eliminate group.top() in bubble mixin, which was used to draw the bubbles in descending order of size, when the group.order() specified the radius. The bubble chart's sortBubbleSize is more general and is lifted to the mixin.

  • v2.1.1 Changes

    • Merges 2.0.1

  • v2.1.0 Changes

    • dc.selectMenu, implementing a <select> menu or multiple-select widget, by Andrea Singh (#771)
    • Heatmap allows customizing the ordering separately from the values, by Matt Traynham (#869 - thanks also to Quinn Lee for #837)
    • Front page stable version automatically read from GitHub, by Enrico Spinielli (#865)
    • Functional-style filter handlers: instead of modifying the array of filters in-place, filter handlers must return the new filter array. This is consistent with the old documention, but a different implementation: any changes to the filters argument will be ignored unless they are returned. This should make filter handlers easier to reason about.

  • v2.0.5 Changes

    • legend highlighting functions of scatter plots would select symbols in sibling charts, causing the symbols and sizes to change (#874)

  • v2.0.4 Changes

    • ↪ Temporary flag stackMixin.evadeDomainFilter to work around issue #949 until it's fixed. The flag completely disables filtering of points by the stack mixin, because the current filtering is wrong. (The correct fix will be included in dc.js 2.1.x when it's ready.)