- 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
domainPadding
on all child components - Adds automatic
domainPadding
for 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
containerComponent
andgroupComponent
props to all components
- Adds
- Changes helper methods to make horizontal bar chart behavior more intuitive
- Supports events on the parent element via the
parent
namespace in theevents
prop. parent
events have access towidth
,height
,style
and the calculatedscale
(withdomain
andrange
already applied). Where applicableparent
events also have access todata
- Shared
parent
events are automatically supported in components that useVictorySharedEvents
by default (i.e. VictoryChart, VictoryGroup, VictoryStack) - When mutating elements via the return from event handlers, mutation objects may now take arrays for
eventKey
to 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
tickFormat
for dates - FIxes a bug related to incorrect axis label placement
- Alters the render order for children of
VictoryChart
so that default axes are always rendered before other children. When axes are explicitly defined children ofVictoryChart
will still be rendered in the order they are defined. - Alters the render order of elements within
VictoryAxis
so that grid elements are rendered before ticks and tick labels - Fixes a bug in
VictoryGroup
that was causing customlabelComponents
of 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
labelComponent
anddataComponent
props. Replaces a customSliceLabel
component withVictoryLabel
to make the api more consistent and predictable. This is a breaking change for custom label components, asVictoryLabel
expects a different set of props than the previousSliceLabel
component. 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
labelComponent
ordataComponent
, so that custom components will have access to the final values. -
events are bound and partially applied prior to being passed as props to
labelComponent
ordataComponent
-
it is now possible to specify
angle
andverticalAnchor
props forVictoryLabel
via 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
data
and/orlabels
keys 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
dataComponent
prop - Enter and exit transitions animate. Enter and exit transition defaults defined
VictoryBar, VictoryArea, VictoryScatter, and VictoryLine. Custom transitions may be
defined via the
onExit
andonEnter
properties of theanimation
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
- Add VictoryArea component
- Add event handling via an
events
prop - Update to lodash 4
- Update
d3-shape
to the latest version (minor breaking changes on interpolation types) - Updates via
builder-victory-component
to support Babel 6 - Provide label text via a
text
prop rather than children
- Add validation of length for
dataAttributes
prop - 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
radium
andlodash
now 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-bar
that 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.