v0.16.0

This release includes major breaking changes related to VictoryZoom

• victory-core/189 and 191
  • Adds VictoryLegend component
• victory-core/190
  • Allows VictoryContainer to render either <g> or <svg> depending on the value of the standalone prop
  • Passes a timer down in context for VictorySharedEvents
  • Event handlers have access to the context they are being called from via an argument
    • i.e. onClick: (event, targetProps, eventKey, context) => {...}
  • Enhances addEvents so that evented components can pick up "parentControllerProps" from parent state
    • useful for VictoryZoomContainer
  • Adds the ability to define callbacks in the events prop that will be called after setState
    • useful for allowing VictoryZoomContainer to call methods like resumeAnimation
• victory-chart/427
  • Adds VictoryBrushContainer
  • Adds VictoryZoomContainer to replace VictoryZoom
  • See pull request for examples
  • Deprecates VictoryZoom
  • Changes default styles for VictorySelectionContainer
  • Adds override-able selectionComponent for VictorySelectionContainer
  • Adds domain and standalone to list of props that get stored in parent state
  • Simplifies and standardizes container rendering across components.

v0.15.0

• Adds VictorySelectionContainer
• Changes when functional styles and props are evaluated (this may be a breaking change)
  Functional styles and props are now evaluated in the primitive components (Point, Bar etc.)
• Supports an active prop on all primitive components that is used when evaluating functional styles and props
• Tooltips now trigger active: true on both labels and data components
• defaultEvents are supported for containerComponents

Alpha

v0.1.1

0.1.1

Alpha

The following components documented and ready to use; API subject to change:

• victory-animation
  • victory-axis
  • victory-bar
  • victory-chart
  • victory-label
  • victory-line
  • victory-pie
  • victory-scatter

Functional styles and functional props (where appropriate) are implemented for all the data primitives (VictoryBar, VictoryLine etc.) and VictoryAxis

Components use d3-modules

Basic code coverage across all Victory components.

We make no promises about any code prior to this release. From this point on, you can expect a regular release schedule (~every two weeks) with detailed release notes. Check out our roadmap for upcoming features