35.11.0 (2021-08-23)

• #1940 - Refactor VictoryChart, VictoryGroup and VictoryStack to take advantage of React.memo.

35.10.1 (2021-08-12)

• #1933 - Remove invalid this references
• #1926 - Use less verbose import / export syntax

35.10.0 (2021-08-04)

• #1910 & #1920 - Upgrade to Webpack 5
• #1915 - Add React as a peerDependency for all Victory packages
• #1907 - Replace default exports with individual exports and namespaced imports
• #1913 - Add optional rx and ry types to the primitive props interface. Thanks @Wesleyzxc!

35.9.3 (2021-07-23)

• #1912 - Adds a more thorough check before calculating barWidth for grouped / stacked charts. Thanks @WaysToGo!

35.9.2 (2021-07-22)

• #1908 - Fixes a bug with barWidth calculation for stacked / grouped bar charts.

35.9.0 (2021-06-24)

Adds a new disableInlineStyles prop to components and primitives to support users who want to style their components by class, or use a CSS in JS solution like styled-components

When the new disableInlineStyles prop is supplied to a component like VictoryBar no styles will be supplied to either data or label components that it renders:

const StyledBar = styled(Bar)`
  fill: purple;
`;
const StyledLabel = styled(VictoryLabel)`
  tspan {
    fill: magenta;
    font-family: Papyrus, fantasy;
  }
`;
function CustomStyledBarChart() {
  return (
    <VictoryChart>
      <VictoryBar
        disableInlineStyles
        labels={[1, 2, 3, 4]}
        dataComponent={<StyledBar />}
        labelComponent={<StyledLabel />}
      />
    </VictoryChart>
  );
}

The disableInlineStyles prop may also be supplied to primitive components for more granular control:

const StyledBar = styled(Bar)`
  fill: purple;
`;
function CustomStyledBarChart() {
  return (
    <VictoryChart>
      <VictoryBar
        labels={[1, 2, 3, 4]}
        dataComponent={<StyledBar disableInlineStyles />}
      />
    </VictoryChart>
  );
}

Related PRs

• #1882 - Thanks @beccanelson!
• #1856 - Thanks @tvsmk!

35.8.1 (2021-05-24)

• #1863 - Fixes a regression impacting stacked bar charts with minDomain introduced in 35.6.0.

35.8.0 (2021-05-19)

• #1858 - domainPadding updates

updates how domainPadding is applied to charts when 1) the additional padding would not result new quadradants being added, or 2) the user has set singleQuadrantDomainPadding={false}. In these cases, domainPadding is applied by calculating a new, smaller range that takes the desired, pixel-based padding into account, and then adding domain padding such that the previous domain fits entirely within the new, smaller range. In most cases, this change will make it much easier to do things like create bar charts where the first bar starts cleanly at the edge of the chart, by setting domainPadding={{ x: myBarWidth / 2 }} This may cause visual changes for charts that use very large values for domainPadding. The domainPadding prop may need to be adjusted

calculates a more exact defaultDomainPadding for grouped bar charts based on the offset, number of bars, and the width of each bar (either from the barWidth prop or from a default barWidth based on the number of bars and the range). Previously, defaultDomainPadding was approximated based only on offset and number of bars.

35.7.2 (2021-05-18)

• #1852 - Fixes a bug related to zooming axes when tickFormat is given as an array. Thanks @jhumbug!

35.7.1 (2021-05-14)

• #1853 - Fixes a bug related to event prop types. Thanks @tvsmk!