victory

A collection of composable React components for building interactive data visualizations

OTHER License

Downloads
37.4M
Stars
11K
Committers
221

Bot releases are visible (Hide)

victory - v36.5.1

Published by becca-bailey over 2 years ago

What's Changed

We are continuing our internal typescript migration, and making some changes to our test infrastructure and build pipeline. This work includes a couple typescript-related bug fixes.

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.5.0...v36.5.1

victory - v36.5.0

Published by becca-bailey over 2 years ago

What's Changed

In 36.5.0 we pushed a lot of changes to our internal tooling. We replaced mocha and enzyme tests with Jest and React Testing Library, migrated some core parts of our codebase to Typescript, and bumped our React version to React 18. 🎉

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.4.1...v36.5.0

victory - v36.4.1

Published by becca-bailey over 2 years ago

What's Changed

This release includes mostly testing improvements, with one bugfix for prop types by @gustaff-weldon.

New Contributors

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.4.0...v36.4.1

victory - v36.4.0

Published by becca-bailey over 2 years ago

What's Changed

Introducing the victory-vendor package

In order to safely upgrade d3-packages while still allowing Node.js users to use ESM imports, we introduced a new package called victory-vendor for babelifying our d3 packages to make them more compatible with Victory. For more info, check out the description here.

This should not make much of a difference for the end user, but there are a couple changes to be aware of. Upgrading d3-scale introduced some minor scaling changes. If you (like us) are using Chromatic or another visual regression testing tool, it may pick up some very small differences in the placement of axes and data points. d3-scale also introduced some changes to the scale.tickFormat function that changes the default formatting for log scales.

Before After

If you are using a log scale and don't wish to use d3's default label formatting, You can use the tickFormat prop on a VictoryAxis component to override this default formatting. https://formidable.com/open-source/victory/docs/victory-axis#tickformat

New Contributors

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.3.2...v36.4.0

victory - v36.3.2

Published by becca-bailey over 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.3.1...v36.3.2

victory - v36.3.1

Published by becca-bailey over 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.3.0...v36.3.1

victory - v36.3.0

Published by becca-bailey over 2 years ago

What's Changed

New Contributors

Full Changelog: https://github.com/FormidableLabs/victory/compare/v36.2.2...v36.3.0

victory -

Published by boygirl over 3 years ago

(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!
victory - 35.8.6

Published by boygirl over 3 years ago

(2021-06-11)

  • #1878 - Downgrade d3-array dependency to correct for babel issue
victory - 35.8.5

Published by boygirl over 3 years ago

(2021-06-09)

  • #1874 - Adds missing allowDraw type definition for VictoryBrushContainer. Thanks @justindomingue!
victory - 35.8.4

Published by boygirl over 3 years ago

(2021-06-01)

  • #1871 - Fixes a bug impacting log scale charts using VictoryVoronoiContainer with voronoiDimension.
victory - 35.8.3

Published by boygirl over 3 years ago

(2021-05-31)

  • #1870 - Fixes a regression impacting offsetX and offsetY props for multi-quadrant charts
victory - 35.8.2

Published by boygirl over 3 years ago

(2021-05-26)

  • #1865 - Improves the interpolation type definition for VictoryArea. Thanks @pmilic021!
victory - 35.8.1

Published by boygirl over 3 years ago

(2021-05-24)

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

Published by boygirl over 3 years ago

(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.

victory -

Published by boygirl over 3 years ago

(2021-05-18)

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

Published by boygirl over 3 years ago

(2021-05-14)

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

Published by boygirl over 3 years ago

(2021-05-12)

  • #1835 - This PR makes VictoryAxis responsible for calculating its own default xOffset, yOffset, orientation, and crossAxis values rather than relying on VictoryChart to determine these values. This change corrects several bugs related to how axes update on charts that use VictoryZoomContainer. We don't anticipate breaking changes with this update, but axis positioning will update differently (more correctly) when zooming. Thanks @jhumbug!
victory - 35.6.4

Published by boygirl over 3 years ago

(2021-05-12)

  • #1850 - Update VictoryTheme type definition to allow adding an optional style prop to VictoryGroup via theme. Thanks @hknowlton!
victory - 35.6.3

Published by boygirl over 3 years ago

(2021-05-10)

  • #1844 - Export missing VictoryAccessibleGroup from the main victory package
  • Security updates