victory-core
Advanced tools
Changelog
31.2.0 (2019-01-27)
Axis improvements
axisValue
prop for both cartesian and polar charts. This prop allows users to position an axis relative to a value on the opposite axis. Values may be given as numbers, dates, or strings. This prop only works for axis components when they are nested within VictoryChart
. Standalone axes can still be positioned using offsetX
and offsetY` props.Removes all deprecated lifecycle methods
componentWillReceiveProps
lifecycle methods and adds shouldComponentUpdate
logic for higher level components. Previously only the lowest level components performed sCU
checks.componentWillMount
with componentDidMount
bug fixes
Changelog
31.1.0 (2019-01-08)
1222 Bugfix: Avoid rendering null values on discrete data
1218 Bugfix: Ensure that calculated domains respect custom baselines for VictoryBar and VictoryArea
1202 Bugfix: Correct missing bar values
1208 Performance: Improve performance in addEventKeys
1211 Performance: Optimize stringMap calculations
1212 Performance: Optimize for preformatted data:
When data objects already contain _x
, _y
(and _y0
where appropriate) and have data accessor props like x="_x"
, data will no longer be formatted by Victory, but will be used as is.
Example:
<VictoryArea
data={[ { _x: 0, _y0: 1, _y: 2 } ...]}
x="_x"
y="_y"
y0="_y0"
/>
1209 Feature: Adds an animationWhitelist
property to the animate
prop. This property should be given as an array of strings. When this prop is given, only the prop names matching the array will be animated, and all other props will be instantaneously updates.
Example:
<VictoryBar
animate={{
animationWhitelist: ["data"]
}}
data={this.state.data}
style={{
data: this.state.style
}}
/>
When this property is not set, the static animationWhitelist
of any given component will be used.