victory-scatter - npm Package Versions

0.6.0 (2016-04-15)

BREAKING CHANGES

• VictoryBar and VictoryArea no longer support multiple datasets.
• VictoryStack and VictoryGroup define stacked and grouped layouts for their children
• Custom data components supported on for VictoryBar, VictoryLine, VictoryScatter, VictoryArea, and VictoryPie via the dataComponent prop
• Enter and exit transitions animate. Enter and exit transition defaults defined VictoryBar, VictoryArea, VictoryScatter, VictoryLine and VictoryPie. Custom transitions may be defined via the onExit and onEnter properties of the animation prop
• Top level svgs are all responsive by default (using svg viewBox). To render a fixed size component, set the standalone prop to false and render the component inside an svg tag

30.5.1 (2018-10-18)

• #1149 Adds onTouchEnd helper for VictoryCursorContainer

0.5.0 (2016-03-15)

• Adds VictoryArea as a data type compatible with VictoryChart.
• Supports custom label components
• Upgrades all repos to lodash 4

0.4.0 (2016-01-31)

• Data Accessors are supported on all relevant components
• Shared code has been factored into VictoryUtil

Breaking Changes:

• VictoryLine and VictoryScatter:
  • plotting functions via the y prop must now be expressed as functions of data rather than functions of x. i.e. y={(data) => Math.sin(data.x)}
• VictoryBar:
  • the domain of the dependent axis will automatically include zero unless a domain is specified via props
  • automatic alphabetic data sorting has been removed
  • automatic 1% domain padding has been removed
• VictoryChart:
  • automatic 1% domain padding has been removed
  • default line data has been removed, so <VictoryChart/> with no additional props will now only render a set of axes with no data

0.3.0 (2016-01-26)

• Demo application now works with hot reloading.
• Application dependencies like radium and lodash now live in components, not in the Builder archetype. This is a breaking change. https://github.com/FormidableLabs/victory/issues/176