All Versions
Latest Version
Avg Release Cycle
8 days
Latest Release
1614 days ago

Changelog History
Page 1

  • v27.1.1 Changes

    June 29, 2018

    -604 Average value and baseline (i.e. y and y0) when calculating voronoi layout

  • v27.1.0 Changes

    June 20, 2018

    ๐Ÿ”จ -555 Refactors how VictoryStack and VictoryGroup interact with child data. Fixes bugs related to stacked and grouped charts in VictoryVoronoiContainer

  • v27.0.0 Changes

    June 05, 2018


    ๐Ÿ’ฅ Breaking Changes

    • ๐Ÿ”จ Refactors utility methods. This is an internal breaking change, but should not be a breaking change for most Victory users. See victory-core/380 for details
    • Upgrades to [email protected]^2.0.0 which changes function comparison. This means that Victory components will update when functions are not equal. This closes several Victory issues, but may cause a slight performance decline

    ๐Ÿ†• New Features

    • โž• Adds minDomain and maxDomain props. These props may be used to set one edge of a domain while allowing the other edge to be determined by data or other props. minDomain and maxDomain override domainPadding.
    • Adds singleQuadrantDomainPadding prop. This prop may be given as a boolean or an object with boolean values for x and y. When this prop is set to false for a given dimension, any domainPadding applied in that dimension will not be constrained to existing quadrants.
  • v26.1.1 Changes

    May 28, 2018

    -599 Add allowDraw boolean prop for VictoryBrushContainer and VictoryBrushLine -598 Fix category bugs -596 Only call onSelectionCleared when selected data exists

  • v26.1.0 Changes

    May 04, 2018

    ๐Ÿ‘ -594 Support functional cornerRadius and objects with cornerRadius defined for "top" and "bottom" 0๏ธโƒฃ -593 Add defaultBrushArea prop with supported options "all", "none" and "disable"

  • v26.0.1 Changes

    April 25, 2018

    -591 Ensure that VictoryVoronoiContainer works correctly with VictoryGroup data.

  • v26.0.0 Changes

    April 21, 2018

    ๐Ÿ’ฅ Breaking Changes

    ๐Ÿ’… -587 Disable styles on data

    ๐ŸŽ This change deprecates Victory's ability to automatically pick up style attributes from the data object. This change will improve performance, but will be a breaking change for many users. Fortunately the upgrade path is simple:

    If your data object looks like

      { x: 1, y: 1, fill: "red", opacity: 0.2 },

    โž• Add the following functional styles:

    style={{ data:  { fill: (d) => d.fill, opacity: (d) => d.opacity } }}

    and everything will work as before.

    -584 Check for labels prop before computing baseProps for labels

    ๐ŸŽ Base props for labels will no longer be pre-calculated unless a labels prop exists. This change improves performance, but it will be a breaking change for users who were using events for adding labels to elements that did not already have them using an event mutation like:

      target: "data",
      eventHandlers: {
        onClick: () => {
          return [{ target: "labels", mutation: () => ({ text: "clicked" }) }];

    If you are using this pattern, you can make labels work as expected by adding a dummy labels prop like: labels={() => null}

    Note: This change does not affect tooltips, which exist, but are invisible until they receive the active prop

    Other changes -589 Audit lodash methods -583 Perf improvement for VictorySelectionContainer

  • v25.2.5 Changes

    April 17, 2018
    • 583 Perf improvements for VictorySelectionContainer and general perf improvements from [email protected]
  • v25.2.4 Changes

    April 13, 2018
    • โšก๏ธ 581 Add react-fast-compare, use in place of lodash.isEqual; add demo that uses and calls shouldComponentUpdate.
  • v25.2.3 Changes

    April 10, 2018
    • 580 Improvements for VictoryBrushLine