- Fixes ordering in stacked and grouped data
- Fixes minor tooltip bugs
- Removes unused
flyoutPropsprop fromVictoryVoronoiTooltip
- Adds support for
VictoryTooltip - Adds
VictoryVoronoicomponent - Adds
VictoryVoronoiTooltip - Moves all primitive rendered components to
victory-corewhere they are exported for external use - Enhances
VictoryGroupso that it can accept adataprop which it will pass to all children. This also allows groups of components to be stacked as one - Adds support for
defaultEventsin any primitive component (i.e.dataComponent,labelComponent) - Adds
onLoadanimations - Adds a
sortKeyprop toVictoryLineto allow sorting by fields other than "x" - Adds a
fixLabelOverlapboolean prop toVictoryAxis. When enables, this feature renders a smaller subset of ticks when the full set of ticks would cause overlapping labels. This feature is currently limited to evenly spaced labels. - Fixes a bug related to
bubblePropertyinVictoryScatter - Allows string data in
VictoryCandlestickandVictoryErrorBar - Performance optimizations
- Refactors ClipPath component to make it easier to write a native version.
This release includes breaking changes for Themes
- Updates the VictoryTheme API to more closely match the props object
- Uses
VictoryTheme.grayscalefor default styling - Fixes a bug related to bar width
- Improves performance by simplifying scale type checking for VictoryBar and VictoryArea
- Fixes default transitions for VictoryBar and VictoryArea
- Adds documentation for VictoryTheme
- Improved animation for continuous data components (i.e. VictoryLine, VictoryArea) using clipPath
- Support for arrays of
childNamein events - Adds
displayNameto all component for ease of debugging / testing
- Fix bug in automatic domainPadding
- Fix bug in generated data
- Fix bug in domainPadding for stacked charts
- Fix colorScale in wrapped components
- Fix animation bug in VictoryCandlestick
- Fix label bug in VictoryCandlestick
- Fix style bug in VictoryCandlestick
- Fix axis orientation for negative charts
- Clean up documentation
- Fix label style bug
- Fix minor errorbar bug
- Fix tick style bug
- Update
victory-core - Removes
reduce-calc-css
- Performance improvements across all components
- Supports asymmetric
domainPadding - Supports
domainPaddingon all child components - Adds automatic
domainPaddingfor grouped bars - Fixes bugs related to log scales
- Fixes a bug related to time scales
- Improves consistency for charts with empty and single value data arrays
- Adds VictoryErrorBar
- Changes default styles to the greyscale theme
- Auto-width enhancement for VictoryBar
- Aria roles for all rendered elements
- Supports negative domain padding
- Adds support for Victory Native
- Adds
containerComponentandgroupComponentprops to all components
- Adds
- Changes helper methods to make horizontal bar chart behavior more intuitive
- Supports events on the parent element via the
parentnamespace in theeventsprop. parentevents have access towidth,height,styleand the calculatedscale(withdomainandrangealready applied). Where applicableparentevents also have access todata- Shared
parentevents are automatically supported in components that useVictorySharedEventsby default (i.e. VictoryChart, VictoryGroup, VictoryStack) - When mutating elements via the return from event handlers, mutation objects may now take arrays for
eventKeyto target several individual elements, or the special value "all" to apply changes to all elements of a particular target type - Fixes a bug related to an incorrect default
tickFormatfor dates - FIxes a bug related to incorrect axis label placement
- Alters the render order for children of
VictoryChartso that default axes are always rendered before other children. When axes are explicitly defined children ofVictoryChartwill still be rendered in the order they are defined. - Alters the render order of elements within
VictoryAxisso that grid elements are rendered before ticks and tick labels - Fixes a bug in
VictoryGroupthat was causing customlabelComponentsof its children to be overridden.
- Pre-calculates and applies VictoryAxis transform to individual elements. This allows custom axis components (i.e.
tickLabelComponent) to be absolutely positioned by overriding position props
- Custom component props get precedence over calculated props
- Fixes bugs related to horizontal bar charts
- Fixes bugs related to label transfroms
- Increases default font sizes for readability
- Adds basic aria roles
- Adds support for custom container elements
- Adds vectorEffect non-scaling-stroke to support responsive charts
- Upgrades to React 15
- Supports wrapped components
- Updates the events API to support shared events This is a breaking change for events
-
improves consistency for
labelComponentanddataComponentprops. Replaces a customSliceLabelcomponent withVictoryLabelto make the api more consistent and predictable. This is a breaking change for custom label components, asVictoryLabelexpects a different set of props than the previousSliceLabelcomponent. See VictoryLabel for more detail. -
Custom components are now supported for all rendered axis elements (axis, axisLabel, grid, ticks, tickLabels)
-
All data and label components now have access to scale so that they can create correctly scaled elements from data i.e. error bars.
-
Functional styles and props are now all evaluated before they are passed as props to
labelComponentordataComponent, so that custom components will have access to the final values. -
events are bound and partially applied prior to being passed as props to
labelComponentordataComponent -
it is now possible to specify
angleandverticalAnchorprops forVictoryLabelvia the style object -
event return values are stored differently on state to facilitate interaction between data and labels. This is a breaking change for events as event handlers must now return an object with with
dataand/orlabelskeys so that these values may be applied appropriately to data and label elements respectively.
- 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 via the
dataComponentprop - Enter and exit transitions animate. Enter and exit transition defaults defined
VictoryBar, VictoryArea, VictoryScatter, and VictoryLine. Custom transitions may be
defined via the
onExitandonEnterproperties of theanimationprop - Top level svgs are all responsive by default (using svg viewBox). To render a fixed size
component, set the
standaloneprop to false and render the component inside an svg tag
- Add VictoryArea component
- Add event handling via an
eventsprop - Update to lodash 4
- Update
d3-shapeto the latest version (minor breaking changes on interpolation types) - Updates via
builder-victory-componentto support Babel 6 - Provide label text via a
textprop rather than children
- Add validation of length for
dataAttributesprop - Remove source-maps from git
- Various documentation fixes
- Provide datum to victory-line custom label
- Upgrade to
victory-core@1.0.0
- VictoryBar, VictoryLine, VictoryScatter, and VictoryAxis are now all part of the VictoryChart repo.
- VictoryChart depends on VictoryCore instead of VictoryUtil, VictoryLabel, and VictoryAnimation individually.
- VictoryChart no longer depends on Radium
- Significant rendering performance improvements
- Supports data accessor functions! more detail
- Application dependencies like
radiumandlodashnow live in components, not in the Builder archetype. This is a breaking change. FormidableLabs/victory#176
- Upgrade to Radium 0.16.2. This is a breaking change if you're using media queries or keyframes in your components. Please review upgrade guide at https://github.com/FormidableLabs/radium/blob/master/docs/guides/upgrade-v0.16.x.md
- Extracted shared code into
victory-util - Increased unit test coverage to ~75%
- update archetype
- Fixed a bug in
victory-barthat was causing the cumulative max on stacked bar charts to be overestimated - Fixed a bug related to date formatting in Firefox
Functional styles and functional props (where appropriate) for child components
using d3-modules instead of all of d3
Basic code coverage.
We make no promises about any code prior to this release.