Note We have moved to per-package
CHANGELOG.md
files since migrating to changesets. Please refer to those individual changelogs for change history.
- Export all types from Victory
- Fix for #2329 (use-animation-state crashing charts)
- Local VSC settings to ignore built files in search
- Remove dependency on use-context-selector by @becca-bailey in #2325
- TS migrate: core utils by @scottrippey in #2289
- Typescript: added types to
victory-vendor
by @scottrippey in #2292 - TypeScript migration: more utils! by @scottrippey in #2299
- TS migrate: prop types by @scottrippey in #2300
- Modularize calculated props helpers by @becca-bailey in #2290
- Build enhancements for move tests PR by @ryan-roemer in #2305
- Chore: generate source maps by @scottrippey in #2307
- TypeScript: Mark
data
asreadonly
by @scottrippey in #2313 - TS migrate: add events by @scottrippey in #2306
- Move tests to root directories by @becca-bailey in #2301
- Update prettier trailing comma rule by @becca-bailey in #2315
- TS: migrate victory-area, victory-chart by @scottrippey in #2314
- TypeScript: migrate
victory
to TypeScript by @scottrippey in #2319 - Use build config for babel by @ryan-roemer in #2321
- Add Victory Bar v37 by @becca-bailey in #2316
- victory-histogram jest tests by @heythisispaul in #2255
- Convert tests for victory error bar by @becca-bailey in #2266
- Typescript Phase 1: Build configuration by @scottrippey in #2260
- victory-vendor: script cleanup and exports enhancements by @ryan-roemer in #2264
- victory-pie jest/rtl tests by @heythisispaul in #2268
- Typescript: Generate proper .d.ts files for Core by @scottrippey in #2271
- Disable func-style eslint rule by @becca-bailey in #2275
- Add victory-scatter tests by @becca-bailey in #2269
- TS migration: victory-primitives by @scottrippey in #2274
- Enable
eslint-comments
by @scottrippey in #2277 - Remove karma tests by @becca-bailey in #2279
- ts-migration: migrated core components to TS by @scottrippey in #2278
- Upgrade React to v18 by @becca-bailey in #2280
- ts-migration: more core by @scottrippey in #2284
- TypeScript: fix a few build issues by @scottrippey in #2285
- [Demo]: Upgrade React Native demo app by @jpdriver in #2288
- Dev: Switch to ye olde yarn1 by @ryan-roemer in #2228
- [docs]: update victory-native introduction by @jpdriver in #2231
- brush container helper jest tests by @heythisispaul in #2229
- Infra: Node updates by @ryan-roemer in #2235
- Docs: Upgrade to latest [email protected] by @ryan-roemer in #2234
- Upgrade dependencies by @ryan-roemer in #2238
- Added helpful error message to 'test' script by @scottrippey in #2248
- Convert victory and victory-chart tests to jest by @becca-bailey in #2246
- Feature/jest candlestick tests by @heythisispaul in #2247
- Add victory core tests by @becca-bailey in #2249
- Add tests for victory-stack, victory-group, and victory-selection-container by @becca-bailey in #2253
- Test migration: victory-tooltip, victory-voronoi by @scottrippey in #2252
- [FIX] Replace references to non-existent PropTypes.function with PropTypes.func by @gustaff-weldon in #2257
- Fix duplicate user props by @becca-bailey in #2256
- migrate existing legend tests to jest by @heythisispaul in #2259
-
Added the ability to add victory charts title and desc props for better accessibility by @shankstee in #2199
-
Bump axios from 0.19.2 to 0.21.2 in /docs by @dependabot in #2188
-
Bump cross-fetch from 3.1.4 to 3.1.5 by @dependabot in #2206
-
add style interface to SliceProps type by @heythisispaul in #2212
-
Add jest and react testing library tests for victory-line and victory-area by @becca-bailey in #2196
-
fix typos in scale prop documentation by @heythisispaul in #2218
-
Bump cross-fetch from 3.1.4 to 3.1.5 by @dependabot in #2213
-
Bump cross-fetch from 3.1.4 to 3.1.5 in /demo/rn by @dependabot in #2207
-
add box plot jest/rtl tests by @heythisispaul in #2225
-
jest and rtl unit tests for bar components by @heythisispaul in #2216
-
Add victory-vendor package for d3 dependencies by @becca-bailey in #2204
-
Vendor in d3 libraries to new package
victory-vendor
and upgrade. Our CommonJS path now uses transpiled versions of thed3-*
libraries while our ESM path continues to use the real underlying dependencies.- Update our tests to only refer to built versions of our libraries (in the past there was a mix of source and built). This means Karma uses the ESM version of libraries while Jest uses the CommonJS versions.
- Added very basic Node.js tests to catch future ESM issues.
- Switch all relative/prefixed import paths to be just
import <name> from "victory-<pkg>"
. - Update various dependencies.
- Added functionality to be able to pass user props to components. Safe… by @dlcartright in #2151
- Bump moment from 2.29.1 to 2.29.2 by @dependabot in #2186
- Add user props tests and remove arbitrary demo props by @becca-bailey in #2172
- Bump minimist from 1.2.5 to 1.2.6 in /demo/rn by @dependabot in #2177
- Add safe user props to all top-level components by @becca-bailey in #2191
- Bump ansi-regex from 3.0.0 to 3.0.1 in /demo/rn by @dependabot in #2190
- Bump plist from 3.0.4 to 3.0.5 in /demo/rn by @dependabot in #2189
- Bump async from 2.6.3 to 2.6.4 in /demo/rn by @dependabot in #2193
- Allow additional props from user, such as
aria-label
anddata-testid
by @becca-bailey in #2192 - Fix Horizontal charts panning at the incorrect rate by @TabithaMaudMM in #2179
- add FAQ for Expo Web apps by @jpdriver in #2121
- Add RegExp array to voronoiBlacklist type by @brendanmorrell in #2127
- Bump url-parse from 1.5.3 to 1.5.10 by @dependabot in #2143
- Bump url-parse from 1.5.3 to 1.5.10 in /demo/rn by @dependabot in #2144
- Bump node-fetch from 2.6.0 to 2.6.7 in /docs by @dependabot in #2075
- Fix TS build 2094 by @matt-hernandez in #2107
- Bump karma from 6.3.14 to 6.3.16 by @dependabot in #2148
- Bump url-parse from 1.4.7 to 1.5.10 in /docs by @dependabot in #2147
- Bump postcss from 7.0.32 to 7.0.39 in /docs by @dependabot in #2146
- Bump prismjs from 1.20.0 to 1.27.0 in /docs by @dependabot in #2145
- Bump lodash from 4.17.19 to 4.17.21 in /docs by @dependabot in #2159
- Bump follow-redirects from 1.14.7 to 1.14.8 by @dependabot in #2095
- Bump karma from 6.3.4 to 6.3.14 by @dependabot in #2092
- Fix font stack and correct margins in docs by @melvin-chen in #2070
- Patch missing text component type by @youPickItUp in #2089
- Bump nanoid from 3.1.28 to 3.2.0 in /demo/rn by @dependabot in #2074
- Patch missing text component type by @becca-bailey in #2097
- fix: android touch events by @zibs in #2071
- feat: Add VictoryNativeBrushLine component by @zibs in #2077
- #2058 - Uncomments type definitions for
VictorySelectionContainer
- #2057 - Adds animationWhitelist prop to animation prop type definition
- #2032 - Fixes bug with victory native touch events in
VictoryBrushContainer
. Thanks @uginy!
- #2015 - Moves
victory-native
into the mainvictory
monorepo - #2006 - Memoize
getCalculatedProps
to improve performance forVictoryStack
andVictoryGroup
- #2010 - Add a
Hooks
namespace for naming consistency
- #1998 - Adds experimental
victory-canvas
package for testing Victory with HTML5 Canvas components.
- #1967 - Updates
events
propTypes forVictoryPie
. Thanks @tgalfin!
- #1940 - Refactor
VictoryChart
,VictoryGroup
andVictoryStack
to take advantage ofReact.memo
.
- #1950 - Update
d3-interpolate
- #1953 - Update
VictoryThemeDefinition
to includehistogram
. Thanks @2metres!
- #1940 - Refactor
VictoryChart
,VictoryGroup
andVictoryStack
to take advantage ofReact.memo
.
- #1910 & #1920 - Upgrade to Webpack 5
- #1915 - Add React as a
peerDependency
for all Victory packages - #1907 - Replace default exports with individual exports and namespaced imports
- #1913 - Add optional
rx
andry
types to the primitive props interface. Thanks @Wesleyzxc!
- #1912 - Adds a more thorough check before calculating
barWidth
for grouped / stacked charts. Thanks @WaysToGo!
- #1908 - Fixes a bug with
barWidth
calculation for stacked / grouped bar charts.
- #1901 Adds a small performance optimization for
VictoryTooltip
. Thanks @beccanelson!
Adds a new disableInlineStyles
prop to components and primitives to support users who want to style their components by class, or use a CSS in JS solution like styled-components
When the new disableInlineStyles
prop is supplied to a component like VictoryBar
no styles will be supplied to either data or label components that it renders:
const StyledBar = styled(Bar)`
fill: purple;
`;
const StyledLabel = styled(VictoryLabel)`
tspan {
fill: magenta;
font-family: Papyrus, fantasy;
}
`;
function CustomStyledBarChart() {
return (
<VictoryChart>
<VictoryBar
disableInlineStyles
labels={[1, 2, 3, 4]}
dataComponent={<StyledBar />}
labelComponent={<StyledLabel />}
/>
</VictoryChart>
);
}
The disableInlineStyles
prop may also be supplied to primitive components for more granular control:
const StyledBar = styled(Bar)`
fill: purple;
`;
function CustomStyledBarChart() {
return (
<VictoryChart>
<VictoryBar
labels={[1, 2, 3, 4]}
dataComponent={<StyledBar disableInlineStyles />}
/>
</VictoryChart>
);
}
Related PRs
- #1878 - Downgrade
d3-array
dependency to correct for babel issue
- #1874 - Adds missing
allowDraw
type definition forVictoryBrushContainer
. Thanks @justindomingue!
- #1871 - Fixes a bug impacting log scale charts using
VictoryVoronoiContainer
withvoronoiDimension
.
- #1870 - Fixes a regression impacting
offsetX
andoffsetY
props for multi-quadrant charts
- #1865 - Improves the
interpolation
type definition forVictoryArea
. Thanks @pmilic021!
- #1863 - Fixes a regression impacting stacked bar charts with
minDomain
introduced in35.6.0
.
- #1858 -
domainPadding
updates
updates how domainPadding
is applied to charts when 1) the additional padding would not result new quadradants being added, or 2) the user has set singleQuadrantDomainPadding={false}
. In these cases, domainPadding
is applied by calculating a new, smaller range that takes the desired, pixel-based padding into account, and then adding domain padding such that the previous domain fits entirely within the new, smaller range. In most cases, this change will make it much easier to do things like create bar charts where the first bar starts cleanly at the edge of the chart, by setting domainPadding={{ x: myBarWidth / 2 }}
This may cause visual changes for charts that use very large values for domainPadding
. The domainPadding
prop may need to be adjusted
calculates a more exact defaultDomainPadding
for grouped bar charts based on the offset
, number of bars, and the width of each bar (either from the barWidth
prop or from a default barWidth
based on the number of bars and the range). Previously, defaultDomainPadding
was approximated based only on offset
and number of bars.
- #1852 - Fixes a bug related to zooming axes when
tickFormat
is given as an array. Thanks @jhumbug!
- #1853 - Fixes a bug related to event prop types. Thanks @tvsmk!
- #1835 - This PR makes
VictoryAxis
responsible for calculating its own defaultxOffset
,yOffset
,orientation
, andcrossAxis
values rather than relying onVictoryChart
to determine these values. This change corrects several bugs related to how axes update on charts that useVictoryZoomContainer
. We don't anticipate breaking changes with this update, but axis positioning will update differently (more correctly) when zooming. Thanks @jhumbug!
- #1850 - Update
VictoryTheme
type definition to allow adding an optional style prop toVictoryGroup
via theme. Thanks @hknowlton!
- #1844 - Export missing
VictoryAccessibleGroup
from the mainvictory
package - Security updates
- #1840 - Improve cursor coordinate type definitions.
- #1837 - Fix a regression introduced in
v35.6.0
impacting inverted domain charts. Thanks @jhumbug!
- #1832 - Add support for custom baselines for
VictoryStack
. Thanks @jhumbug! - #1833 - Add missing scale prop type for container type definitions.
- #1827 - Points fully outside of a chart domain are now given null values to prevent them from being rendered. Exceptions are made for continuous chart types like
VictoryArea
andVictoryLine
. This PR also includes a fix for animations so that animating data always reaches its final state before a new animation begins. Thanks @jhumbug!
- #1819 - Improve built
dist
output
- #1815 - Fix a bug affecting
VictoryBrushContainer
withallowResize
set to false, and usedefaultBrushArea="move"
by default whenallowResize
is set to false.
- #1812 - Update
VictoryTooltip
types to allow users to set single dimensions for thecenter
prop
- #1807 - Add missing
handleWidth
type toVictoryBrushContainer
interface. Thanks @aknaut!
- #1800 - Add missing
id
prop toVictoryLabelProps
interface. Thanks @nielsboecker!
- #1799 - Improve event prop interface. Thanks @loganwedwards!
- #1789 - Skip the parent namespace when caching event state in
VictorySharedEvents
. Thanks @the-kwisatz-haderach!
-#1784 - - Add more font widths for the textsize util. Thanks @eatyourpeas!
- #1780 - Remove unused
type
prop from primitive components used byVictoryAxis
andVictoryPolarAxis
- #1782 - Fix type definition for the
getPath
prop used by thePoint
primitive. Thanks @ASmartLynx!
-#1767 - Adds support for rx
and ry
props on the Background
primitive component. Thanks @NgoKnows!
-
#1765 - Adds "cross" symbol for
VictoryScatter
and thePoint
primitive. -
#1766 - Allows the
bin
prop onVictoryHistogram
to accept arrays of negative numbers. Thanks @NgoKnows!
- #1761 - Add more font widths for the textsize util. Thanks @dlabrecq!
- #1755 - Export
Portal
type
- #1751 - Add missing static
defaultEvents
toVictoryTooltip
types. Thanks @beccanelson!
- #1750 - Add missing
className
prop to theBackground
primitive component. Thanks @beccanelson!
- #1748 - Thank you @Hypnosphi!
This release adds a concept of global events that are attached to window
rather than to any of the elements rendered by Victory components. Global events are only supported for "parent" events that would normally be attached to svg
elements rendered by Victory's containerComponents. Events that should be global can be flagged by including onGlobal
in the name of the event handler. So, for example, use onGlobalMouseUp
rather than onMouseUp
to create a global mouse up handler.
VictoryBrushContainer
now uses global events in its defaultEvents
so that brushing continues even as the user's mouse moves outside of the chart area.
- #1743 - Add a
role
prop forVictoryContainer
- #1738 - Stop timers used by
VictoryAnimation
when there are no active subscriptions. Thanks @noVerity! - #1739 - Improve types related to styles and themes across all packages.
- #1740 - Replace all instances of
Object.keys
with lodashkeys
for consistency.
- #1733 - Fix TS definitions affection multi-line labels and tooltip orientations. Thanks @paolostyle!
- #1732 - Fix a bug affecting stacked histograms. Thanks @keithbro!
- #1728 - Use exact versions for Victory interdependencies to make it easier for users to specify exact versions
- #1726 - Decrease throttle on
VictoryCursorContainer
for smoother movement. Thanks @Alexander-AJ-Berman!
-
#1724 Fixes a regression introduced in
35.3.0
affecting charts whose dimensions are updated via auseEffect
hook -
#1723 - Avoids unnecessary re-renders caused by empty events. Thanks @Hypnosphi!
- #1715 Adds a dependency on
json-safe-stringify
inVictorySharedEvents
- #1716 Changes how event updates are cached to support React Strict Mode
-
#1708 - This PR adds
ariaLabel
to Victory's primitive components (VictoryLabel
,Area
,Bar
etc.). This new prop can take a string or a function that expected to return a string, and addsaria-label
attributes to svg elements Victory renders. This PR also addstabIndex
andaria-label
props toVictoryClipContainer
, and creates a newgroupContainer
,VictoryAccessibleGroup
, which renders ag
tag and an optionaldesc
tag along with its other children.VictoryAccessibleGroup
also takesaria-label
andaria-describedby
props. Thanks @ljones87 for all the hard work on this new feature! -
#1709 - Adds default
onFocus
andonBlur
event handlers toVictoryTooltip
so that users can trigger tooltips by tabbing through the chart elements whentabIndex
is set.
- #1707 - Respects user-provided props on the label component
VictoryVoronoiContainer
renders, includingtext
,style
,flyoutStyle
,width
andheight
- #1710 - Adds support for providing functions to the
angle
prop onVictoryLabel
- #1711 - Fixes a bug related to applying angles to labels whose position is set by
datum
rather than coordinate.
- #1693 - Add
aria-labelledby
andaria-describedby
props toVictoryContainer
. Thanks @elliotdickison!
- #1692 - Adds a unique key prop for chart backgrounds
- #1690 - Fixes a minor positioning bug in label backgrounds
- #1688 - Fixes vertical alignment issue for labels. Thanks @Hypnosphi!
- #1685 - Adds an optional
preserveAspectRatio
prop toVictoryContainer
, and usesheight: "100%"
rather thanheight: "auto"
, giving users finer control over how Victory's svgs are positioned and scaled within their containers.
- #1677 - Add missing TS exports from the main victory package. Thanks @sarah-vanderlaan!
- #1657 - Fix bug in
ouiaSafe
prop onVictoryContainer
- #1654 - Add optional OUIA props for
VictoryContainer
. Thanks @dlabrecq!
- #1652 - Fix a bug related to voronoi radius. Thanks @sseppola!
-
#1648 - Fix a bug effecting
backgroundStyles
when using functional styles. Thanks @chacestew! -
#1649 - update lodash dependency
- #1645 - Fix bug in text size approximation. Thanks @nburt!
- #1640 - Update package readmes with new docs links
- #1631 - Correct types for
TextSize
utility. Thanks @jlismore!
- #1628 - Correct typescript error
This release introduces new label features and makes improvements to themes. This release includes breaking style changes. Please double check your label and tooltip styles when upgrading. Polar axes and pie charts may be particularly impacted.
-
VictoryLabel
now supports label backgrounds, which are rendered asrect
elements behind your labels. Backgrounds are styled via the newbackgroundStyle
prop onVictoryLabel
. This prop may be given as a style object, or an array of objects for styling multi-line labels. Background elements are sized for their corresponding text elements, but padding may also be added with thebackgroundPadding
prop, which accepts a single number, an object with values for "top", "bottom", "left" and "right", or an array of either of these for adding background padding to multi-line labels. -
VictoryTooltip
has a newflyoutPadding
prop that may be used to add padding between the edge of the flyout and the label within it. TheflyoutPadding
prop may be given as a single number of as an object with values for "top", "bottom", "left" and "right". This is a breaking change, asstyle.padding
no longer adds padding between the flyout and its label. Both of Victory's built-in themes have been altered so that tooltips getflyoutPadding={5}
by default. -
VictoryPie
now supports thelabelPlacement
prop used in polar charts. Possible values are "vertical" "parallel" and "perpendicular". When not given, vertical labels are rendered as before. -
Themes now support
polarAxis
,polarDependentAxis
, andpolarIndependentAxis
namespaces that are merges with the less specificaxis
,dependentAxis
, andindependentAxis
themes as appropriate.
-
Changes Victory's default branch from
master
tomain
🖤 -
Textsize
approximations have changed, and are much more accurate in most cases. This may be a breaking change for layouts that depended on approximated text size -
Tooltip themes are now correctly merged with label styles and props.
-
VictoryPolarAxis
elements are now rendered relative to the origin independently, rather than being translated as a group. This allows for correct positioning of elements withinVictoryPortal
This may be a breaking change for custom components inVictoryPolarAxis
-
Corrects the
labelPosition
prop onVictoryPie
(previouslystartAngle
andendAngle
were inverted) This is a breaking change -
Alters
material
andgreyscale
themes. The following theme updates may cause breaking style changes- Uses more widely available default fonts for labels
- Reduces default label padding for
boxplot
andcandlestick
- Adds
polarDependentAxis
settings to thematerial
theme - Zero padding on from
tooltip
styles override label styles on all other theme namespaces. This means that tooltips pointers will now all start exactly at the data element they correspond to by default. To alter this behavior, either 1) provide a different theme, 2) alter padding in via label styles like so:or<VictoryBar style={{ labels: { padding: 5 } }} labelComponent={<VictoryTooltip />} />
<VictoryBar labelComponent={ <VictoryTooltip style={{ padding: 5 }} /> } />
- #1583 - Initial label background work
- #1625 - Label and theme improvements
- #1627 - Switch CI to main
-#1620 - Allow granular voronoiPadding
. Thanks @dlabrecq!
-#1607 - Add missing containerRef type. Thanks @NgoKnows!
- #1605 - Fixes padding for axes with non-standard orientations. Thanks @glvnsky!
-
#1604 - Fixes offsets for groups of stacked bars. Thanks @cneltyn!
-
#1599 - Fixes a bug causing incorrect cursor behavior
onMouseLeave
. Thanks @NgoKnows!
- #1592 - Cache
sharedEvents
to improve performance in evented containers. Thanks @NgoKnows!
- #1588 - Improve perfomance by reducing string map calculations. Thanks @NgoKnows!
- #1576 - Add more types for primitive components. Thanks @maddles
- #1580 - Improve histogram tooltip positioning for
VictoryVoronoiContainer
- #1581 - Prevent
VictoryVoronoiContainer
from rendering tooltips with empty text
-#1575 - Allow the id
prop for VictoryLabel
to be given as a function. Thanks @amyboyd!
- #1573 - Add explicit dependencies on
d3-scale
andreact-fast-compare
forvictory-histogram
. Thanks @Mike-Dax!
- #1572 - Add missing
backgroundComponent
type
- #1570 - Correct missing
victory-histogram
dependency
- #1568 - Correct export for VictoryHistogram
- #1531 - Adds a
VictoryHistogram
component. Huge thanks to @NgoKnows for this new feature!
<VictoryHistogram
binSpacing={1}
bins={[0, 20, 50, 500]}
data={[
{ value: 1 }, { value: 1 }, { value: 2 }, { value: 3 } ...
]}
x="value"
/>
Histogram bins may be defined with the bin
prop, which takes either an array of bin edges, or a single number which corresponds to an approximate number of bins. VictoryHistogram
is meant to work with continuous data, and expects a data prop as an array of objects with x values. By default, histogram bins will be laid out with no spaces between bins, but the optional binSpacing
prop may be provided to change this behavior. Additional documentation and examples will be coming soon.
- #1558 - Adds a
backgroundComponent
forVictoryChart
that will be rendered ifVictoryChart
'sstyle
component includesbackground
styles. TheBackground
component renders arect
for cartesian charts and acircle
for polar charts that is correctly sized and positioned to fill the entire range of the chart. Thanks @maddles and @wparsons!
- #1563 - Fixes a regression introduced in 34.1.3 that was effecting charts with the
domain
prop defined for a single dimension. - #1564 - Fixes a regression introduced in 34.1.3 that was causing
domainPadding
to not be applied to stacked and grouped charts withdomain
props defined.
Update typescript types for all Victory components. A huge thanks to @maddles @wparsons and @kale-stew for this work. This release includes the following PRs
#1557, #1556, #1554, #1552, #1551, #1550, #1547, #1546, #1543, #1538, #1536, #1535, #1534, #1533, #1532, #1530,#1529, #1528, #1527, #1526, #1525, #1524, #1522, #1521, #1520, #1519, #1515, #1514, #1512, #1510, #1508
- #1494 - Performance improvements targeted at reducing the number of calculations performed for nested charts (charts using the VictoryStack and VictoryGroup wrappers).
- #1496 - Add missing package dependencies to support Yarn PnP. Thanks @Mike-Dax!
- #1485 - Better typescript linting and minor bug fix for
VictoryChart
types
- #1481 - Add typescript types from the
definitely-typed
project so that we can maintain them more easily going forward
- #1474 - Adds an
activePoints
prop toVictoryTooltip
whichVictoryVoronoiContainer
supplies to itslabelComponent
. Thanks @jotak!
This version uses the context API introduced in [email protected]
- #1462 - Updates to the new context API. Thanks @fabianishere!
- 1453 - Correctly handle null values in tooltips with custom flyoutComponents. Thanks @alecf!
- #1450 - Skips
stringMap
computation when data is preformatted (i.e. data uses has_x
and_y
values and accessors). Thanks @na9da!
- #1443 - Adds a
mouseMoveThreshold
prop forVictoryBrushContainer
to prevent accidental redraws. Thanks @Hypnosphi! - #1448 - Removes an unnecessary check for svg target in
VictoryBrushContainer
onMouseLeave
- #1447 - Adds support for function values for the
labelPosition
prop onVictoryPie
- #1434 Ensure the correct handles are used in
VictoryBrushArea
when axes are inverted. Thanks @Hypnosphi! - #1435 Adds a "move" option for the
defaultBrushArea
prop inVictoryBrushContainer
. When this option is selected, clicking outside of the brush area will pan the brush to a the area the user clicked without resizing the brush. Thanks @Hypnosphi!
- #1425 Corrects padding on zero value tooltips.
- #1423 Make sure
VictoryChart
does not override axis orientations defined in themes. - #1422 Use the correct domain in the
onBrushEnd
domain callback. - #1420 Fixes behavior with
allowZoom
prop. Thanks @Hypnosphi!
- #1409 Updates
delaunay-find
to0.0.4
to correct incorrect nearest values for sets of points with collinear values. Corrects bugs inVictoryVoronoiContainer
- #1404 Adds a11y improvements
- corrects behavior of VictoryContainer so that it only adds aria-labelledby and aria-describedby attributes when there are actually title and / or desc elements that are rendered (controlled by the title and desc props on VictoryContainer
- adds a tabIndex prop to all primitive components that Victory renders (i.e. VictoryLabel, Bar etc). This prop may be given as a number or a function of other props
- adds a desc prop to all primitive components. This prop may be given as a number or a function of other props
-
#1401 - Fixes a bug affecting automatic candle coloring
-
#1402 - Fixes a bug affecting user-provided
containerRef
callbacks
- #1387 - Add support for custom functions for the
interpolation
prop. Thanks @sanniassin!
-
1384 - Fixes a bug affecting functional
cornerRadius
onVictoryTooltip
-
1385 - Adds
pointerOrientation
prop onVictoryTooltip
to make it possible to control which side of the tooltip the pointer extends from independent of which side of the data point the entire flyout is oriented towards. This prop only became sensible with the addition ofcenter
andcenterOffset
props added in[email protected]
- #1379 - Fixes a bug affecting functional
padAngle
prop inVictoryPie
- #1378 - Fixes a bug affecting function labels in
VictoryPie
- #1375 - Evaluates / calculates some props early so they are available when functional props are being evaluated. Most notably,
text
is evaluated before any other functional props forVictoryLabel
so it may be used to determine things like style, etc.
Changes for functional props and styles:
Related PR: #1360
Functional props like labels
and functional styles will now be called with a single argument instead of datum
and active
. The argument passed to functional props and styles will be an object containing all the props that control the rendering of the the target the prop applies to. Including things like datum
, active
, index
, data
, scale
, etc. We hope this will give users a lot more flexibility and control. In most cases, this change should be very straightforward to apply
old:
labels={(d) => `x: ${d.x}`}
new
labels={({ datum }) => `x: ${datum.x}`}
Gotchas:
- Some of the props passed into functional props and styles may themselves be functions. These will not be evaluated, because we have no way to determine evaluation order. So, if you create a
cornerRadius
function that depends onbarWidth
, do not also makebarWidth
a function of some other prop. - A few props that take functions do not follow this pattern. These include data accessor functions like
y
andx
, andtickFormat
. The arguments for these props have not changed.
Changes for VictoryCandlestick
labels
Related PR: #1295
VictoryCandlestick
now has granular support for labels corresponding to each portion of the candle. The current labels
and labelComponent
props will be joined by new props corresponding to each part of the candle.
New props
lowLabels
lowLabelComponent
highLabels
highLabelComponent
openLabels
openLabelComponent
closeLabels
closeLabelComponent
This will be a breaking change affecting the positioning of the default label
. In earlier versions, the default label was positioned above the candle, it will now be positioned next to the center of the candle.
To use older label positioning, use highLabels
/ highLabelComponent
rather than label
/ labelComponent
. If you are using tooltips with VictoryCandlestick
, you will need to register a custom event to trigger your highLabels
tooltip:
example:
<VictoryCandlestick
highLabels={({ datum }) => datum.high}
highLabelComponent={<VictoryTooltip />}
events={[{
target: "data",
eventHandlers: {
onMouseOver: () => ({ target: "highLabels", mutation: () => ({ active: true }) }),
onMouseOut: () => ({ target: "highLabels", mutation: () => ({ active: false }) })
}
}]}
/>
The style
prop for VictoryCandlestick
now also has namespaces for the new labels in addition to the current labels
namespace. When both labels
and specific label styles (e.g. highLabels
) are provided, the styles will be merged
Changes for VictoryVoronoiContainer
Related PR: #1371
Before this version VictoryVoronoiContainer
had limited functionality for mouse-following tooltips, and for constraining a tooltip to the chart area, but it was only usable for multi-point tooltips (with voronoiDimension
), and was not user configurable. This version aims to correct these limitations:
mouseFollowTooltips
: This new boolean prop onVictoryVoronoiContainer
determines whether the labels should follow the mouse position or snap into place. (Note that in charts usingvoronoiDimension
, the tooltip still follows the mouse in the non-voronoiDimension
, as demonstrated in the charts below (both withvoronoiDimension="x"
)
- constrained tooltips: multi-point tooltips rendered by
VictoryVoronoiContainer
will no longer be constrained to the chart area by default. Instead, add theconstrainToVisibleArea
prop toVictoryTooltip
to enable this behavior for both multi-point and single point tooltips: example:
containerComponent={
<VictoryVoronoiContainer
labelComponent={<VictoryTooltip constrainToVisibleArea />}
/>
}
Changes for VictoryTooltip
and VictoryLabel
Related PR:#1371
The changes we wanted to make to support new behaviors in VictoryVoronoiContainer
required some changes to VictoryTooltip
and VictoryLabel
New props for VictoryTooltip
:
-
constrainToVisibleArea
is a boolean prop that, when true, will alter the position of the tooltip so that it exactly fits within the svg Victory renders. The tooltip's center will be moved, but the pointer will remain pointing at the associatedx
,y
value of the tooltip. When this prop is set to true,pointerLength
may not be respected -
center
is a prop that may be given as an object with values or functions for "x" and "y". When this prop is set, it will position the center of the tooltip (centered around the main body of the tooltip, minus the pointer). When this prop is not set, it will be calculated from other props such asx
,y
,pointerLength
, etc. This prop was added to enable mouse-following tooltips inVictoryVoronoiContainer
. -
centerOffset
is a prop that may be given as an object with values or functions for "x" and "y". When this prop is set, the center of the tooltip will be offset by some amount from the x, y value it points to, resulting in a slanted pointer. When this prop is set,pointerLength
will not be respected (because the pointer will be slanted) -
flyoutHeight
(formerlyheight
): This optional prop determines the height of the tooltip flyout (minus pointer). The name of this prop was changed so that it would not conflict with theheight
prop now passed toVictoryTooltip
by its parents -
flyoutWidth
(formerlywidth
): This optional prop determines the width of the tooltip flyout (minus pointer). The name of this prop was changed so that it would not conflict with thewidth
prop now passed toVictoryTooltip
by its parents -
width
: the overall width of the parent svg. This prop will be passed down from any victory component that usesVictoryTooltip
as a label -
height
: the overall height of the parent svg. This prop will be passed down from any victory component that usesVictoryTooltip
as a label
Changes Affecting VictoryLabel
and VictoryTooltip
- The
x
andy
values passed to labels by their parent components have all been adjusted so that their values match the position of the data point they correspond to. All padding is now accounted for in thedx
anddy
props instead of being added directly tox
andy
. This will be a breaking change for anyone who is wrapping label components and relying on thex
andy
props they receive, or providing their owndx
/dy
props. These breaking changes may take a bit of manual adjustment to correct, but we hope this change will make label positioning easier to reason about in the long run.
Other Changes
We have been concurrently working on improving performance and the stability of events in victory-native
. The following changes have been added to support these efforts:
Related PR: #1373
- A
prependDefaultAxes
boolean prop has been added toVictoryChart
. This prop will be set true by default invictory-native
to reduce the possibility of axis elements to interfere with events. - Invisible ticks and grids will no longer be rendered unless they have events attached to them. This is again to reduce interference with events.
Related PR: #1365
- Swapped out React component primitives (
Bar
,Path
etc) with for function primitives to match performance-improving changes invictory-native
. (This is a breaking change for anyone extending fromvictory
components)
#1368 Ensures that animations finish for unmounting components. Thanks @fbarbat!
#1363 Fix regression affecting createContainer
. Thanks @stefanscript
#1362 Fix scroll wheel interaction in newer versions of Chrome.
#1361 Updates to lodash^4.17.15
. Thanks @tomciopp
#1346 - Fixes a bug which was preventing VictoryVoronoiContainer
from activating all coincident points when no voronoiDimension
was set
#1345 - Uses updated delaunay-find
instead of d3-voronoi
in VictoryVoronoiContainer
#1344 - update lodash
#1343 - revert to d3-voronoi
#1322 - Replaces d3-voronoi
with d3-delaunay
in VictoryVoronoiContainer
#1333 - replace d3-delaunay
with delaunay-find
#1306 - Calls eventKey
functions with both datum
and index
#1304 - renames private variables to reduce potential for conflict
#1302 - Fixes slight vertical offset for elements rendered in VictoryPortal
#1299 - Support rendering array labels on separate lines. Previously labels={() => {"one", "two"}}
would stringify the array rather than rendering it on two lines
#1292 Reverses the render order for children of VictoryStack
. This may cause minor visual changes for stacked charts, but should be an improvement for most users, as stokes and labels will no longer be cut off by higher stacks being rendered after lower stacks
#1293 Fixes a bug related to custom labelComponent
rendering in VictoryLegend
#1278 Adds regex support for the voronoiBlacklist
prop. This prop may now be given as an array of strings or an array of regex patterns. Thanks @narinluangrath!
#1271 Replace PropTypes.exact
with PropTypes.shape
#1266 Fixes area stroke on polar charts
Horizontal Chart Improvements!
The goal of this change is to make it possible to turn any existing chart into a horizontal chart by adding the horizontal
prop to the chart without needing to alter any other props.
- supports horizontal versions of all chart types without needing to alter data
- supports all event containers for horizontal charts
- enforces consistency across props that take x and y values so that the
x
value always refers to the independent dimension, and they
value always refers to the dependent dimension. - the orientation of
VictoryAxis
components is no longer tied to whether or not they are thedependentAxis
Breaking Changes
Most Horizontal Charts
The change in how props with x and y values are treated (i.e. scale
, domain
, etc) will be a breaking change for most horizontal charts. In most cases, reversing the x
and y
values of props you are providing to your horizontal chart will be sufficient to correct the change. For example:
<VictoryChart horizontal scale={{ x: "log" }} domain={{ y: [4, 9] }}>
<VictoryBar
data={[
{ x: 5, y: 0.1 },
{ x: 6, y: 1 },
{ x: 7, y: 10 },
{ x: 8, y: 100 }
]}
/>
</VictoryChart>
Should be changed to:
<VictoryChart horizontal scale={{ y: "log" }} domain={{ x: [4, 9] }}>
<VictoryBar
data={[
{ x: 5, y: 0.1 },
{ x: 6, y: 1 },
{ x: 7, y: 10 },
{ x: 8, y: 100 }
]}
/>
</VictoryChart>
Props affected by this change are: scale
, domain
, maxDomain
, minDomain
, domainPadding
, and categories
Horizontal Charts with Event Containers
Dimension props such as brushDimension
have changed so that they always refer to the dimension of the target variable (x for the independent variable, and y for the dependent variable). For example, a VictoryBrushContainer
component with brushDimension="x"
will move and expand only in the independent dimension regardless of whether the chart is horizontal.
Props affected by this change are: brushDimension
, cursorDimension
, selectionDimension
, voronoiDimension
, and zoomDimension
Horizontal Charts with Custom dataComponents
The position values (i.e. x
, y
, x0
, y0
) supplied to custom dataComponents
from components like VictoryChart
will be scaled for the layout of the horizontal chart. Users who rely on these values may need to flip them or adjust them depending on their use case
Horizontal VictoryBoxPlot
Previously VictoryBoxPlot
required data to be flipped (x values flipped with y values) in order to plot horizontal charts. This is no longer required, and providing data in this format will no longer work correctly. To correct for this change, it should be sufficient to flip the data used in horizontal charts
- 1247 Adds support for
labelOrientation
as an object forVictoryBoxPlot
. Thanks @mAAdhaTTah
Axis improvements
- 1244 Supports the
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 withinVictoryChart
. Standalone axes can still be positioned usingoffsetX
and offsetY` props. - 1240 Allows multiple independent axes in a single chart
Removes all deprecated lifecycle methods
- 1239 Removes all
componentWillReceiveProps
lifecycle methods and addsshouldComponentUpdate
logic for higher level components. Previously only the lowest level components performedsCU
checks. - 1228 Replaces
componentWillMount
withcomponentDidMount
bug fixes
- 1243 Prevents
VictoryBrushLine
active brushes from overflowing the brush area when a chart is zoomed - 1241 Fixes a regression effecting immutable data rendering
- 1227 Fixes a minor regression effecting parent event keys introduced by 1211
-
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 likex="_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 theanimate
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.
- 1200 Export
defaultStyles
fromVictoryLabel
. Thanks @rudasoftware!
- 1182 Bugfix: fixes incorrect cornerRadius
- 1185 Bugfix: corrects bug in zooming for horizontal charts
- #1177 Adds support for controlling
radius
,innerRadius
,cornerRadius
,padAngle
,sliceStartAngle
andsliceEndAngle
for each individual slice of a pie:
Details:
The Slice
primitive used by VictoryPie
now takes radius
, cornerRadius
, innerRadius
, padAngle
, sliceStartAngle
and sliceEndAngle
props. Each of these props may be given as number or a function of datum
and active
. padAngle
, radius
, cornerRadius
and innerRadius
will be passed down from props on VictoryBar
, but sliceStartAngle
and sliceEndAngle
must be defined directly on the Slice
instance, These values should be given in degrees. To make these values easier to use as functional props, startAngle
, endAngle
, and padAngle
(in degrees) are added to each datum
passed into Slice
. (If your data already has these properties they will not be overridden)
Breaking Changes
The Slice
primitive will still take a pathFunction
prop, but this prop will no longer be provided by VictoryPie
. This will not be a breaking change for most users. This will only affect users who were wrapping the Slice
component and making use of the pathFunction
prop provided by VictoryPie
Users who were providing their own pathFunction
prop to Slice
should not be effected.
- #1178 Bugfix: single point charts with time scale data are appropriately centered
- #1171 Bugfix:
fixLabelOverlap
no longer causes errors with stringtickValues
- #1152 Bugfix:
barWidth
functions were not being correctly evaluated - #1158
cornerRadius
improvements forVictoryBar
- Artifacts caused by
cornerRadius
values larger than the height of the bar have been corrected cornerRadius
now supportstopLeft
,topRight
,bottomLeft
andbottomRight
values in addition to existing values. This is not a breaking change. These values may be used alongside existing values fortop
andbottom
, but more specific values will override less specific values.
- Artifacts caused by
- #1149 Adds
onTouchEnd
helper forVictoryCursorContainer
- #1135 - Allow closed paths for cartesian and polar
VictoryLine
- #1130 - Adds a
labelPosition
prop toVictoryPie
with optionsstartAngle
,endAngle
andcentroid
(default). Thanks @sikolio! - #1126 - Ensures that
onBrushDomainChangeEnd
is called for dragging and panning actions. Thanks @jeloagnasin!
- #1127 - Fixes a bug with cornerRadius when defined as a function
- #1124 - Changes cursors in
VictoryBrushContainer
whenallowResize
andallowDrag
are set to false. Thanks @erick2014
- #1121 - Adds a separate
onBrushDomainChangeEnd
event handler forVictoryBrushContainer
that is only called on mouse up events. Thanks @jeloagnasin!
- #1104 - Bugfix: correct sorting and stacking horizontal bars with categorical data
- #1088 - Bugfix: don’t ignore angle: 0 for text styles
- #1091 - Fix inconsistent defaultBrushArea behavior. Thanks @bees
- #1093 - Remove trailing whitespace and incorrect zeroes in transform strings
- #1094 - Support direction prop for VictoryLabel and Text primitive
- #1096 - Fix bug in horizontal zooming and panning
- #1101 - Fix arguments in
VictoryVoronoiContainer
label function. Thanks @evsheino
- #1072 Fixes a bug related to correctly stacking grouped components
- #1074 Fixes a bug that was causing time scale data to be ignored by
VictoryVoronoiContainer
when calculating voronoi layouts - #1076 Implements a whitelist based on
static role
when calculating data and domain from child components. - #1077 Prevents
VictoryZoonContainer
from downsampling stacked data - #1078 Adds
barWidth
andcandleWidth
props toVictoryBar
andVictoryCandlestick
. AddscandleRatio
prop toVictoryCandlestick
- #1079 Adds
onBrushCleared
callback prop forVictoryBrushContainer
- #1080 Changes how tooltips are deactivated so that multiple sources may reactivate tooltips (i.e. multiple triggers in
VictorySharedEvents
or direct triggers and voronoi triggers) #1081 Legends now render title and border when data is an empty array (previously nothing was rendered)
-1061 Fixes default bar width for chart with only one bar. Thanks @40x -1062 Improvements for victory-native
stability
- Supports
clipPath
prop on all primitive components - generates keys based on
name
orid
prop. -1063 Makesprop-types
a real dependency
Victory is becoming a monorepo!
This will not be a breaking change for the majority of users, especially those importing all components from the main victory
npm package
Breaking Changes
- The
Axis
/Grid
primitive component has been renamedLineSegment
- Victory no longer supports git installs
victory-chart
andvictory-core
packages export different sets of packages than they used to. See the complete list below
New Package Organization
victory
exports everything exported from the packages below[email protected]
exportsVictoryAxis
[email protected]
exportsVictoryArea
andArea
[email protected]
exportsVictoryBar
andBar
[email protected]
exportsVictoryBoxPlot
[email protected]
exportsVictoryBrushContainer
,BrushHelpers
andbrushContainerMixin
[email protected]
exportsVictoryBrushLine
[email protected]
exportsVictoryCandlestick
andCandle
[email protected]
exportsVictoryChart
[email protected]
still exports several packages that are used by several Victory components:VictoryAnimation
VictoryClipContainer
VictoryContainer
VictoryLabel
VictoryPortal
andPortal
VictoryTheme
VictoryTransition
- Several primitive components:
Arc
,Border
/Box
,Circle
,ClipPath
,LineSegment
(formerlyAxis
/Grid
),Line
,Path
,Point
,Rect
,Text
,TSpan
,Whisker
- Several utilities:
addEvents
,Axis
,Collection
,CommonProps
,Data
,DefaultTransitions
,Domain
,Events
,Helpers
,Immutable
,LabelHelpers
,Log
,PropTypes
,Scale
,Selection
,Style
,TextSize
,Timer
,Transitions
,Wrapper
[email protected]
exportscreateContainer
,combineContainerMixins
andmakeCreateContainerFunction
[email protected]
exportsVictoryCursorContainer
,CursorHelpers
andcursorContainerMixin
[email protected]
exportsVictoryErrorBar
andErrorBar
[email protected]
exportsVictoryGroup
[email protected]
exportsVictoryLegend
[email protected]
exportsVictoryLine
andCurve
[email protected]
exportsVictoryPie
andSlice
[email protected]
exportsVictoryScatter
[email protected]
exportsVictorySelectionContainer
,SelectionHelpers
andselectionContainerMixin
[email protected]
exportsVictorySharedEvents
[email protected]
exportsVictoryStack
[email protected]
exportsVictoryTooltip
andFlyout
[email protected]
exportsVictoryVoronoi
andVoronoi
[email protected]
exportsVictoryVoronoiContainer
,VoronoiHelpers
andvoronoiContainerMixin
[email protected]
exportsVictoryZoomContainer
,RawZoomHelpers
,ZoomHelpers
andzoomContainerMixin
VictoryPie -182 Adds optional radius
and origin
props to VictoryPie
. The radius
prop should be given as a single number. The origin
prop should be given as an object with number values specified for "x" and "y". When these props are not given, radius and origin are determined by width
, height
, and padding
as previously.
VictoryCore -390 Breaking Change for other Victory packages
This PR changes how the exported helper reduceChildren
operates, and removes getDomainFromGroupedData
-392 Make sure transforms are applied to primitive components
VictoryChart -555 Refactors how VictoryStack
and VictoryGroup
interact with child data. Fixes bugs related to stacked and grouped charts in VictoryVoronoiContainer
Breaking Changes
- Refactors utility methods. This is an internal breaking change, but should not be a breaking change for most Victory users. See victory-core/380 for details
- Upgrades to
react-fast-compare@^2.0.0
which changes function comparison. This means that Victory components will update when functions are not equal. This closes several Victory issues, but may cause a slight performance decline
New Features
- Adds
minDomain
andmaxDomain
props. These props may be used to set one edge of a domain while allowing the other edge to be determined by data or other props.minDomain
andmaxDomain
overridedomainPadding
. - Adds
singleQuadrantDomainPadding
prop. This prop may be given as a boolean or an object with boolean values for x and y. When this prop is set tofalse
for a given dimension, anydomainPadding
applied in that dimension will not be constrained to existing quadrants.
VictoryCore -374 Consistent PropTypes
for clipId
-373 Evaluate styles for polar bars -372 Support top and bottom cornerRadius for bars. Support functional cornerRadius -371 Evaluate Whisker styles -370 Refactor to remove lifecycle methods
VictoryChart -594 Support functional cornerRadius
and objects with cornerRadius
defined for "top" and "bottom" -593 Add defaultBrushArea
prop with supported options "all", "none" and "disable" -591 Ensure that VictoryVoronoiContainer
works correctly with VictoryGroup
data.
BREAKING CHANGES
Disable arbitrary styles from data This change deprecates Victory's ability to automatically pick up style attributes from the data object. This change will improve performance, but will be a breaking change for many users. Fortunately the upgrade path is simple:
If your data object looks like
data={[
{ x: 1, y: 1, fill: "red", opacity: 0.2 },
...
]}
Add the following functional styles:
style={{ data: { fill: (d) => d.fill, opacity: (d) => d.opacity } }}
and everything will work as before.
Limit Pre-calculating label props Base props for labels will no longer be pre-calculated unless a labels prop exists. This change improves performance, but it will be a breaking change for users who were using events for adding labels to elements that did not already have them using an event mutation like:
events={[{
target: "data",
eventHandlers: {
onClick: () => {
return [{ target: "labels", mutation: () => ({ text: "clicked" }) }];
}
}
}]}
If you are using this pattern, you can make labels work as expected by adding a dummy labels prop like: labels={() => null}
Note: This change does not affect tooltips, which exist, but are invisible until they receive the active
prop
All Changes VictoryCore -364 Perf: Remove style whitelist filter. -369 Ensure state -368 Audit lodash methods -367 Simplify state filtering -365 Perf: Return early when label content is null or undefined -362 Perf: Filter falsey mutations from state
VictoryChart -587 Disable styles on data -584 Check for labels prop before computing baseProps for labels -589 Audit lodash methods -583 Perf improvement for VictorySelectionContainer
VictoryPie -176 Disable styles on data -177 Audit lodash methods
VictoryCore -343 Changes the render order of lines and areas in the Area
primitive -344 bug fix for VictoryTransition
with fewer children -334 Add Whisker
primitive for VictoryBoxPlot
VictoryChart -557 VictoryBoxPlot
-575 Stack datasets with differeing domains -574 Refactor helper method exports
VictoryPie -168 Refactor helper method exports
VictoryChart -573 Use fallback styles in VictoryBrushLine
VictoryCore -339 Adds a "minus" option for Point
VictoryChart -571
- Adds
selectionBlacklist
toVictorySelectionContainer
- Adds
activateData
andactivateLabels
toVictoryVoronoiContainer
(true by default) - Adds
activateSelectedData
toVictorySelectionContainer
(true by default) -572 Changes behavior oflabels
inVictoryVoronoiContainer
labels
is now called withpoint, index, points
instead ofpoint, active
. This will not be a breaking change for most users, as this function was only called when labels wereactive
-570 Add "minus" option forVictoryScatter
symbol
prop -569 Fixes a bug increateContainer
-568 AddsbrushAreaWidth
prop forVictoryBrushLine
-567 Fixes brushArea active state inVictoryBrushLine
-565 Prevent re-renders with disable prop
VictoryCore -341 Improve sCU logic for primitive components
VictoryChart -563 stopPropagation
when panning or selecting VictoryBrushLine
-565 Adds disable
prop to all interactive containers and addon components
-victory-chart/562 Bugfix for VictoryCursorContainer
-918 Add `sideEffects: false
VictoryCore -337 Add sideEffects: false
-338 Fix bar path bug in Firefox
VictoryChart -560 Add sideEffects: false
-561 Bugfix for createContainer
VictoryPie -167 Add sideEffects: false
Major Features
VictoryBrushLine
for multi-brush support
Breaking Changes
Candle
expects a new set of props fromVictoryCandlestick
- The
Line
component has been renamed toAxis
/Grid
- Internal methods for all Victory primitive components have changed. This will be a breaking change for users who are extending primitive components, including
victory-native
.
VictoryCore -336 Fixes key names for ErrorBar
-325 Adds a getDimension
static method for VictoryLegend
-326 Adds a fallback prop for VictoryLegend
titleOrientation
-327 Use pointerEvents: "painted"
for grid styles -328 Adds inline
prop for VictoryLabel
-329 Bugfix add-events
-330 Adds wickStyleWidth
prop for Candle
This is a breaking change as it changes the expected props for Candle
-331 Bugfix portal rendering -333 Whitelist style attributes -335 Update primitives
This is a breaking change for victory-native
and anyone extending primitive components.
*This is a breaking change for for the Line
component. Renamed Axis
/ Grid
VictoryChart -551 Bux fixes and improvements for VictoryStack -553 Allow renderInPortal to be false for tooltips in VictoryVoronoiContainer
-554 Add support for wickStrokeWidth
in VictoryCandlestick
This is a breaking change as the expected props for Candle
are changed -556 Fixes undefined context variable -558 Allow func
PropType for color
on VictoryGroup
-559 Implement VictoryBrushLine
and use updated primitive components
**This is a breaking change for anyone using the Line
primitive. It has been renamed to Axis
/ Grid
.
**This may be a breaking change for anyone who was extending Victory primitives**
VictoryPie -166 Update Victory primitives
VictoryCore
- 324 Adds support for external event mutations
- Adds
externalEventMutations
prop toVictorySharedEvents
and all components enhanced with theadd-events
HOC externalEventMutations
prop format:
externalEventMutations: PropTypes.arrayOf(PropTypes.shape({ callback: PropTypes.func, childName: PropTypes.oneOfType([ PropTypes.string, PropTypes.array ]), eventKey: PropTypes.oneOfType([ PropTypes.array, CustomPropTypes.allOfType([CustomPropTypes.integer, CustomPropTypes.nonNegative]), PropTypes.string ]), mutation: PropTypes.func, target: PropTypes.oneOfType([ PropTypes.string, PropTypes.array ]) })) ``` *Note:* `eventKey` and `target` must be specified for externalEventMutations. When using `extenalEventMutations` with shared events (_i.e._ events on VictoryChart etc), `childName` is also required.
- Adds
Note: The callback
supplied to externalEventMutations
should be used for clearing mutations. This is crucial for animating charts
-323 Add support for immutable data structures
note: compatible with [email protected]
and will be compatible with [email protected]
when released
VictoryChart
- 550 Fixes a bug related to voronoi tooltip positioning
- 549 Fixes a prop type warning for
categories
supplied toVictoryAxis
- 548 Adds a
voronoiBlacklist
prop toVictoryVoronoiContainer
- 547 Fixes downsampling in
VictoryZoomContainer
with function plotting - 545 Fixes a bug related to panning in
VictoryZoomContainer
- 544 Adds support for external event mutations
- 543 Fixes a bug related to dates in
VictoryBrushContainer
- 545 Fixes a bug in
VictoryZoomContainer
- 542 Adds support for immutable data note: compatible with
[email protected]
and will be compatible with[email protected]
when released
VictoryPie
VictoryCore
- 320 Adds
rowGutter
and support for asymmetric gutters for bothgutter
androwGutter
inVictoryLegend
- 322 Adds support for a
sortOrder
prop with values "ascending" or "descending"
VictoryChart
- 540 Adds
allowSelection
boolean prop forVictorySelectionContainer
(true by default) - 541 Implements
sortOrder
prop with "ascending" and "descending" options
VictoryPie
- 160 Add
sortOrder
prop
VictoryCore
- 316
- adds
cornerRadius
prop forBar
- adds
barRatio
prop forBar
- removes rounding from calculated paths
- fixes a domain bug for negative bars and areas
- adds
VictoryChart
- Update infrastructure for React 16
- victory-chart/534 Add
allowResize
andallowDrag
props forVictoryBrushContainer
Breaking Changes
- victory-chart/527
- adds an
invertAxis
prop forVictoryAxis
that will flip the domain of a given axis when true. Changing theorientation
prop of a given axis will no longer flip the domain on that axis unless theinvertAxis
prop is also set. tickFormat
as an array will set the number of ticks iftickValues
are not given.tickValues
will be forced to a unique array.tickFormat
may still have non-unique values.tickCount
will now always have an effect when set. Previously, this prop would do nothing whentickValues
were provided. NowtickCount
will downsample any array provided to eithertickValues
ortickFormat
.
- adds an
Other Changes
VictoryChart
- 529
VictoryChart
no longer calculatestickValues
ortickFormat
for axis children.stringMap
andcategories
are passed to axis components instead. - 528 and 530 Remove numeric keys from styles
- 526 Always set animation state
VictoryCore
- 310 Add
getPath
prop forPoint
to support custom path calculation - 311 Fix bug in
TextSize
- 313 Use
tickFormat
for calculating a stringMap when appropriate - 314 Theme changes: Change
pointerEvents
to "visible" for grids
- victory-core/307 Adds a default className for containers
- victory-core/308 Fix borderWidth on error bars
- victory-core/309 Fix non-responsive container styles, add container ref
- victory-chart/524 Fix naming changes for
VictoryCursorContainer
BREAKING CHANGES:
victory-core/299 Containers are now rendered in parent divs. This may be a breaking change for parent styles.
victory-chart/518 Naming changes for container props
VictoryBrushContainer
dimension
->brushDimension
selectionComponent
->brushComponent
selectedDomain
->brushDomain
selectionStyle
->brushStyle
onDomainChange
->onBrushDomainChange
VictoryCursorContainer
dimension
->cursorDimension
onChange
->onCursorChange
VictorySelectionContainer
dimension
->selectionDimension
VictoryVoronoiContainer
dimension
->voronoiDimension
VictoryZoomContainer
dimension
->zoomDimension
onDomainChange
->onZoomDomainChange
Other Changes
- victory-core/300 Fixes path rendering for decimal values
- victory-core/302 Adds an
alignment
prop for<Bar/>
so that bars may be rendered with "start", "middle" (default), or "end" alignment relative to their value. - victory-core/304
VictoryLabel
positioning is calculated fromdatum
whenx
andy
positioning props are not provided. This features supports data annotations - victory-core/305 Adds a
groupComponent
prop forVictoryPortal
. This prop is used byVictoryZoomContainer
so that children rendered withinVictoryPortal
may still be clipped when zooming
- victory-chart/516 Ensure that
VictoryZoomContainer
respectsclipId
- victory-chart/517
VictoryZoomContainer
andVictoryVoronoiCOntainer
should ignore legend children - victory-chart/519 Adds an
alignment
prop forVictoryBar
so that bars may be rendered with "start", "middle" (default), or "end" alignment relative to their value. - victory-chart/520 Adds an
allowPan
prop forVictoryZoomContainer
. (Default true) - victory-chart/521 Changes how children of
VictoryZoomContainer
are clipped to enable better zooming forVictoryPortal
- victory-chart/522 Fixes a bug in
VictoryZoomContainer
that effected time scale charts withzoomDomain
specified
- victory-core/297 Adjusts automatic width in
VictoryLegend
- victory-core/296 Fixes layout bug in
VictoryLegend
BREAKING CHANGES: Styling and layout for VictoryTooltip
and VictoryLegend
are impacted
- victory-core/293 This may be a breaking change
Removes the default theme from
VictoryTooltip
. See PR for additional details. - victory-core/294 This may be a breaking change Improvements for
VictoryLegend
- Adds a legend border that can be styled or replaced with a custom component
- new props:
borderComponent={<Border/>}
andborderPadding
- new style / event namespace: "border"
- new props:
- Adds new primitive component
Border
which renders arect
element- props: common props +
width
,height
,x
andy
- props: common props +
- Adds a legend title with supporting props for positioning and centering titles
- new props: title, titleComponent={}, titleOrientation, centerTitle
- new style / event namespace: "title"
- Adds a legend border that can be styled or replaced with a custom component
- victory-core/295 Fixes deprecation error for React 16
VictoryCore
- 289 Bugfix: createContainer + containerId
- 287 Allow users to override
touchAction
style in containers - 286 bugfix: tooltip positioning with
dx
anddy
VictoryChart
- 510 Render axis line under other axis elements
VictoryPie
- 153 Bugfix for asymmetric padding
VictoryCore
- 285 bugfix: tooltips with
activateData
- 278 Support touch events
- 280 Fix tooltip rendering in VictoryPortal
- 281 bugfix: functional label padding
- 282 bugfix: fix "unknown props on
<g>
tag" warning - 283 Allow boolean value for animate prop
- 284 Sort arrays by "key" when animating. See #684
- 274 Fixes automatic bar width calculation for horizontal bars
- 275 Adds an optional
containerId
prop for all Victory containers - 276 Adds
downsample
method forData
VictoryChart
- 504 bugfix: padding bug in
VictoryCursorContainer
- 505 Support touch events on all containers
- 506 Add
props
argument forVictoryVoronoiContainer
callbacks - 507 bugfix: Support array styles for
VictoryLabel
when it is used as a direct child ofVictoryChart
or other wrappers - 508 Add support for
animate
as a boolean prop - 509 Add
props
as the last argument for all container callbacks - 502 Fix bug in
VictoryZoomContainer
- 503 Add downsample option for
VictoryZoomContainer
- 504 Fix padding bug in
VictoryCursorContainer
VictoryPie
VictoryCore
- 267 Correct single-point domain logic
- 268 Correct stacked domain logic
- 269
VictoryLabel
accepts percentage values forx
andy
- 270
VictoryLegend
supports events. Also enforces consistent parent styles as other Victory components. Breaking style change for VictoryLegend - 272 Aggressive
shouldComponentUpdate
logic for evented Victory components Breaking change for some components usingaddEvents
VictoryChart
- 496
VictoryZoomContainer
improvements for real-time, updating data - 497 bugfix: apply
domainPadding
to explicit domains - 498
VictoryAxis
determines its own defaulttickFormat
- 499 Fix label prop merge order for
VictoryVoronoiContainer
labels - 500 Support performance improvements for evented components e.g.
VictoryArea
,VictoryBar
...
Victory:
- 651 Support Webpack 3 and ES6 exports
VictoryCore:
VictoryChart:
- 495 Support Webpack 3 and ES6 exports
- 494 Ensure that
tickFormat
has access totick
,index
, andticks
- 491 Corrects dependent axis for
innerRadius
- 490 Fixes a bug in domain calculation for polar axes
- 488
VictoryZoomContainer
only updates the domain in the dimension it controls - 489 Adds support for
innerRadius
on polar charts
VictoryPie:
- 149 Support Webpack 3 and ES6 exports
- 148 Translates individual slices rather than an entire group translation for pie and labels
Minor bug fixes:
VictoryCore
- victory-core/255 style typo
- victory-core/257 single point domain calculation bug
- victory-core/259 Area render bug
- victory-core/260 Area render order
- victory-core/515 Bugfix for ARIA title and desc. Now both have unique IDs.
- victory-core/262 Consistent widths for polar bars. This change may require style adjustments to maintain visual continuity
VictoryChart
- victory-chart/482 Add
minBubbleSize
prop toVictoryScatter
- victory-chart/484 Remove inappropriate interpolation options for
VictoryArea
andVictoryLine
- victory-chart/487 Fix a bug in
VictoryPolarAxis
domain calculation
- victory-core/240 Polar Charts
- victory-chart/466 Polar Charts
- victory-chart/475 Brush and Zoom fixes
- victory-chart/476 Zoom Improvements
Breaking Changes
- Removes default bar width from themes
- Changes how default bar widths are calculated
- Changes render methods for
Area
,Bar
andCurve
primitives (Breaking change forvictory-native
and others extending primitives) - Changes function signatures for
Selection.getDomainCoordinates
andSelection.getDataCoordinates
(Breaking change forvictory-native
)
Overview
- Supports polar charts by adding the
polar
prop to charts. - Polar charts are supported for
VictoryArea
,VictoryChart
,VictoryGroup
,VictoryLine
,VictoryScatter
VictoryStack
andVictoryVoronoi
- Polar charts are supported for
VictoryBar
, but horizontal (radial) bars are not yet supported - Polar charts work with
VictoryVoronoiContainer
- Polar charts work with
VictorySelectionContainer
, but the dimension prop is not supported for polar selections - Polar charts work with
VictoryZoomContainer
, but zooming is limited to centered radial zooming. Panning has no effect. - Polar-specific default animations for
VictoryLine
andVictoryArea
- horizontal polar charts are not yet supported
VictoryCandlestick
andVictoryErrorBar
do not yet work with polar chartsVictoryCursorContainer
does not yet work with polar chartsVictoryBrushContainer
does not work with polar chartsVictoryZoomContainer
has limitations for polar charts
Planned additional work
- Support for radial bars
- Support for spider charts (i.e. linear grid lines rather than arcs on polar charts)
- Support separate theming for polar charts (at least axes)
- Support for a polar version of
VictoryCursorContainer
- Minimal support for polar versions of
VictoryCandleStick
andVictoryErrorBar
(Elements will be correctly positioned and angled, but path elements will not be altered to reflect curvature, i.e. candles will still berects
rather than arc paths) - Investigate hollow polar charts
Details
- Adds
VictoryPolarAxis
with new props:axisAngle
startAngle
,endAngle
, andlabelPlacement
- Adds
polar
,startAngle
,endAngle
, anddefaultPolarAxes
props forVictoryChart
- Adds
polar
,origin
, andrange
props to all chart types. - Adds
defaultPolarTransitions
static methods toVictoryLine
andVictoryArea
- Uses
LabelHelpers
to simplify allhelper-methods
- Adds a new
Arc
primitive which is used for polar axes and grid lines - Adds
polar
andorigin
props to rendered components (primitives,VictoryLabel
,VictoryClipContainer
VictoryContainer
) - Supports radial areas for
Area
andCurve
. These props have no effect for cartesian charts - Adds an
openPath
prop forCurve
. This prop is used to determine whether radial curves should be closed. Curves are closed by default, but when this prop is set to true they will not be. This prop has no effect for cartesian charts - Supports polar bars in the
Bar
primitive. (Angular bars only, radial bars are not yet supported) - Adds a
labelPlacement
prop toVictoryLabel
andVictoryTooltip
. Values are "parallel", "perpendicular", and "vertical". These flags help to appropriately position labels in polar charts. Polar charts will use "parallel" label placement by default. Cartesian charts will only use "'vertical" placement. - Adds support for circular clipPath
- Adds support for polar animation transitions for continuous chart types. During
onLoad
, all points grow from zero. DuringonEnter
andonExit
new points are added / removed at the location of an adjacent point to keep path interpolation as smooth as possible. This implementation obviates the need for radial clip-path animations for these chart types. before
andafter
callbacks foronLoad
,onEnter
andonExit
are now called withdatum
,index
, anddata
instead of onlydatum
.- Adds
LabelHelpers
- Adds helper methods for polar charts
Breaking Changes -victory-chart/471 Passes the string value of ticks to the tickFormat
function rather than the associated index. This may be a breaking change for users who are using categorical data and formatting tick values by index
New Features -victory-chart/474 Adds support for a y0 accessor so that users can have granular control over the baseline of components like VictoryArea
-victory-core/246 Adds an itemsPerRow
prop to VictoryLegend
to support automatic legend wrapping
Minor Changes -victory-chart/472 Fixes a bug that was causing VictoryGroup
to override styles on any independent VictoryLabel
children -victory-core/244 Passes missing datum
and index
props to Flyout
-victory-chart/250 Audits shouldComponentUpdate
logic for all primitive components so that changes to optional props like className
will cause components to re-render. -victory-pie/146 Rounds label positions for VictoryPie
- victory-chart/469 Adds
VictoryCursorContainer
- victory-core/241 Adds optional
title
andesc
props toVictoryLabel
- victory-core/243 Improvements to
VictoryContainer
- Automatic
overflow: "visible"
for elements rendered inVictoryPortal
(tooltips) VictoryContainer
no longer rendersg
tags (this was causing confusion with evented containers)- Default responsive styles are now
width: "100%"
height: "100%"
(fixes a bug in safari) - Changes the merge order for responsive styles so that
width
andheight
attrs may be overridden
- Automatic
- victory-core/244 adds missing
index
anddatum
props toFlyout
- victory-core/245 fixes
dy
calculation inVictoryLabel
BREAKING CHANGE
- Updates to
react@^15.5.0
- Uses separate
prop-types
package - Projects using Victory must also depend on
prop-types
- Removes
VictoryVoronoiTooltip
- Supports combining container behaviors with the
createContainer
method. - Individual
combineContainerMixins
are also exported. - For more detail, see victory-chart/453
victory-chart/447 Improves performance for container components
Minor bug fixes -508 -509 -510 -517 -520
- Support multi-repo tooling
(VictoryVoronoiContainer)
BREAKING CHANGES
VictoryTooltip
no longer automatically adds theactive
prop to data when hovered. To turn this behavior on, set the newactivateData
boolean prop onVictoryTooltip
- Deprecates
label
in favor oflabels
inVictoryLine
andVictoryArea
, allowing individual data labels for these components like in other Victory components. This will be a breaking change for anyone using thelabel
prop inVictoryLine
orVictoryArea
. Series labels will need to be configured manually. VictoryZoomContainer
now zooms both x and y dimensions, use the propdimension="x"
to return to the old behaviorVictoryZoomContainer
now centers zoom behavior on the mouse position rather than the center of the chartVictoryZoomContainer
has a minimum zoom level of the extent of the domain / 1000. Set a custom minimum with theminimumZoom
prop, which takes an object with numeric values for x and/ or y.VictoryBrushContainer
no longer hasdimension="x"
as the default value.
Deprecation Notice
VictoryVoronoi
and VictoryVoronoiTooltip
have been replaced by VictoryVoronoiContainer
and will be deprecated in version 0.20.0
VictoryTooltip
no longer automatically adds theactive
prop to data when hovered. To turn this behavior on, set the newactivateData
boolean prop onVictoryTooltip
- Adds a
theme
prop toVictoryContainer
so that custom containers may pick up themes from their parents - Removes default
title
anddesc
props fromVictoryContainer
- Adds support for providing
text
as an array forVictoryLabel
- Adds support for providing
style
as an array forVictoryLabel
so that each line of a multi-line label may be styled independently - Changes how null data values are handled by
Area
andCurve
primitives - Adds a
reduceChildren
method toHelpers
to ensure order consistency when working with nested children
- implements data sorting for all components with a
sortKey
props
- Adds
VictoryVoronoiContainer
for hover events (tooltips).VictoryVoronoiContainer
has several benefits overVictoryVoronoi
andVictoryVoronoiTooltip
- Supports multi-dataset voronoi
- Much better performance (voronoi polygons are not actually rendered, so the number of nodes rendered is dramatically lower)
- Supports multi-data tooltips
- Supports rectangular selections with a dimension prop
i.e.
dimension="x"
creates vertical hover areas for every unique x value in all child data
- Deprecates
label
in favor oflabels
inVictoryLine
andVictoryArea
, allowing individual data labels for these components like in other Victory components. This will be a breaking change for anyone using thelabel
prop inVictoryLine
orVictoryArea
. Series labels will need to be configured manually - Changes how null values are handled in
VictoryArea
, and groups all line and area segments (i.e. split by null values) into the sameeventKey
, so that they operate as a single line for the purposes of events.
- Supports x and y dimension zooming in
VictoryZoomContainer
- Adds a
minimumZoom
prop forVictoryZoomContainer
- Zooming centers on mouse position rather than in the center of the chart
- Adds a
translateY
prop forClipPath
to support x, y zoom behavior - Removes default
clipPadding
inClipPath
- victory-core/195
- Fixes null event state bug
- victory-chart/431
- Sets a maximum amount of scale per zoom event for smoother interaction with fast onWheel events
- victory-chart/429
- Throttles
onWheel
andonMouseMove
events on Victory container components - Exports container event helpers
This release includes major breaking changes related to VictoryZoom
- victory-core/189 and 191
- Adds
VictoryLegend
component
- Adds
- 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) => {...}
- i.e.
- Enhances
addEvents
so that evented components can pick up "parentControllerProps" from parent state- useful for
VictoryZoomContainer
- useful for
- Adds the ability to define callbacks in the events prop that will be called after
setState
- useful for allowing
VictoryZoomContainer
to call methods likeresumeAnimation
- useful for allowing
- Allows
- victory-chart/427
- Adds
VictoryBrushContainer
- Adds
VictoryZoomContainer
to replaceVictoryZoom
- See pull request for examples
- Deprecates
VictoryZoom
- Changes default styles for
VictorySelectionContainer
- Adds override-able
selectionComponent
forVictorySelectionContainer
- Adds
domain
andstandalone
to list of props that get stored in parent state - Simplifies and standardizes container rendering across components.
- Adds
- 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 forcontainerComponents
- Fixes date handling in VictoryZoom
- Adds support for className in primitive components
- Fixes minor animation bugs
- Fixes bugs in VictoryZoom
- Adds
pointerEvent: "none"
to tooltip
This may be a breaking change for animating VictoryArea and VictoryLine. Animation behavior is changed.
- Change how animations behave for continuous data i.e. VictoryArea and VictoryLine
- clipPath curtain will never be smaller than the range except during
onLoad
- clipPath curtain will never be smaller than the range except during
- Simplify transitions code
- Ensure that animations and transitions use the global timer passed in context or create their own
- Fix
bypassAnimation
bug - Ensure that clipPath width and height are never negative
- Fix timer issues and export VictoryZoom
- Temporarily revert global animation timer and VictoryZoom changes
- Export VictoryZoom
- Add global animation timer
- Add VictoryZoom
- Stricter npmignore
- Uses
publishr
to reduce npm installed package size #413 - Fixes a bug where label padding was not being applied to tick labels #408
- Removes default tick padding in themes
- Changes how the domain is calculated when there is only one data point, or when the minimum and maximum of the data is equal in a given dimension #407
- Removes hard-coded
<g>
fromVictorySharedEvents
#402 - Ensures that ticks array is not empty after filtering zeroes for crossed axes
- Fixes naming for "stack" and "group" roles
- Allows npm 2 installs
- Fixes incorrect Aria roles
- Removes support for
children
for VictoryLabel. Usetext
instead - Upgrades all d3 packages
- Greater consistency of props for props passed to primitive components
- Adds
VictoryPortal
which renders any child elements in a top level portal container if it exists VictoryTooltip
usesVictoryPortal
by default- Adds
VictoryClipContainer
which renders children in a group container with aclipPath
ifclipPath
props exist. This component is used for animating continuous data types likeVictoryLine
. It should not be used for custom clipPaths. VictoryArea
andVictoryLine
useVictoryClipContainer
as theirgroupComponent
- Removes
clipPath
properties fromVictoryLine
andVictoryArea
- Extracts event logic into a new inverted inheritance higher order component
addEvents
which is used by all chart components - Fixes a bug in
VictoryTransition
that was causing unnecessary rerendering - Exposes
Data
,Domain
,Scale
, and other helpers - Fixes date related domain bugs
- Fixes stacking for time scale data
- Supports separate theming for x and y axes
- Fixes ordering for stacked and grouped data
- Fixes broken tooltips in Safari
- Fixes tooltip fill bug
- Corrects
propTypes
inVictoryTooltip
- Removes unused
flyoutProps
prop inVictoryVoronoiTooltip
This is a breaking change for label placement in VictoryPie
- Adds support for
VictoryTooltip
- Adds
VictoryVoronoi
component - Adds
VictoryVoronoiTooltip
- Moves all primitive rendered components to
victory-core
where they are exported for external use - Enhances
VictoryGroup
so that it can accept adata
prop which it will pass to all children. This also allows groups of components to be stacked as one - Adds support for
defaultEvents
in any primitive component (i.e.dataComponent
,labelComponent
) - Adds
onLoad
animations - Adds a
sortKey
prop toVictoryLine
to allow sorting by fields other than "x" - Adds a
fixLabelOverlap
boolean 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
bubbleProperty
inVictoryScatter
- Allows string data in
VictoryCandlestick
andVictoryErrorBar
- Performance optimizations
This is a breaking change for themes across all components and for label placement in VictoryPie
- Updates VictoryTheme API, uses
VictoryTheme.grayscale
for default styling - Alters label placement in VictoryPie so that when label styles include padding, the
innerRadius
of the pie does not effect label placement. - Adds a
displayName
to all components for ease of debugging - Improves animation for continuous data components (i.e. VictoryLine, VictoryArea) using clipPath
- Improves performance by simplifying scale type checking for VictoryBar and VictoryArea
- Supports for arrays of
childName
in events - Fixes a bug related to bar width
- Fix PropType warnings in React 15.3+
- Add animationInfo as 2nd argument to victory-animation child function call
- Fixes minor domainPadding bugs for stacked and grouped charts
- Fixes a bug in generated data
- Fix animation and style bugs for VictoryCandlestick
- Fix layout bug effecting negative axes in VictoryChart
- Update docs
- Fix minor error bar bug
- Fix minor axis style bugs
Breaking Changes
- Default styles and some default props have changed across all components in this release.
VictoryTheme
- All Victory components support a
theme
prop that can be used to define styles and props across different component types. victory-core
includes the material theme
VictoryCandlestick
- The new
VictoryCandlestick
component may be used standalone or in conjunction withVictoryChart
. It has an identical API and feature set as other chart compatible components with the exception of thedata
and data accessor props.VictoryCandlestick
expectsdata
in the form[{x: value, high: NUMBER, low: NUMBER, open: NUMBER, close: NUMBER}...]
, and includes data accessor propsx
,high
,low
,open
, andclose
.
VictoryErrorBar
- The new
VictoryErrorBar
component may be used standalone or in conjunction withVictoryChart
. It has an identical API and feature set as other chart compatible components with the exception of thedata
and data accessor props.VictoryErrorBar
expectsdata
in the form[{x: value, y: value, errorX: ERR, errorY: ERR}...]
, WhereERR
is a number or a two value array for asymmetric errors.VictoryErrorBar
also includes data accessor propserrorX
anderrorY
.
VictoryNative
- Changes have been made across all components in order to support victory-native.
VictoryNative
has an identical API toVictory
, and reuses most of the code. Changes made toVictory
to supportVictoryNative
are all non-breaking, and minimal. They include the addition of agroupComponent
prop in all components (which defaults to<g>
), removing svg transforms whenever possible in favor of absolute positioning, and code reorganization.
Performance improvements
- Low-hanging performance improvements included in this release:
- Replace
Object.assign
with lodashassign
- Replace
map
/reduce
array methods with length-cachedfor
loops in methods responsible for rendering elements
- Replace
Misc
- Improvements for
domainPadding
domainPadding
is supported in all components compatible withVictoryChart
- Negative and asymmetric
domainPadding
is supported. Example:domainPadding={{x: [-20, 20], y: 50}}
- Grouped bar charts get automatic
domainPadding
so that bars wont overflow axes in most cases.
- Adds Aria roles for all rendered elements
- Fixes bugs related to log scales
- Fixes a bug related to time scales
- Improves consistency for charts with empty and single value data arrays
- Removes
reduce-calc-css
as a dependency
Events enhancements
- Supports events on parent containers (i.e. top level
<svg>
) via theparent
namespace in theevents
prop - In VictoryChart,
parent
events have access towidth
,height
,style
and the calculatedscale
(withdomain
andrange
already applied). Where applicableparent
events also have access todata
- in VictoryPie
parent
events have access towidth
,height
,style
and the calculatedslices
and the calculatedpathFuncton
- 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 - Associates parent events with child events via a
container
prop onVictorySharedEvents
. This is useful where shared events are automatic as inVictoryChart
,VictoryStack
andVictoryGroup
VictoryContainer
- Supports a custom
containerComponent
in all chart types. containerComponent
defaults to the newVictoryContainer
which renders an<svg>
with defaulttitle
anddescription
aria roles
Full support for horizontal bar charts
- Fixes bugs related to axis layout of horizontal bar charts
Misc improvements
- Adds
vectorEffect: "non-scaling-stroke"
where applicable for improved readability in responsive charts - Increases default
fontSizes
for improved readability - Removes parent transform from
VictoryAxis
so that custom elements can be absolutely positioned more easily - Alters
VictoryAxis
render order to that grids are rendered under labels - Alters the render order of default axes in
VictoryChart
so that default axes will render under data. Explicitly defined axes will still render in whatever order they are defined - Adds a
cornerRadius
prop toVictoryPie
to enable pie slices with rounded corners. Thanks @judikdavid! - Renders all pie slices before labels to prevent slices from overlapping labels
Bug fixes
- Fixes a bug related to transforms for
VictoryLabel
- Fixes a bug in
VictoryGroup
that was causing customlabelComponents
in its children to be overridden. - Fixes a bug related to incorrect an incorrect default
tickFormat
being applied to dates
- Upgrades to React 15
- Supports wrapped components in
VictoryChart
- Adds
VictorySharedEvents
wrapper for coordinating events between supported Victory Components. An annotated example of the new events API:
<VictorySharedEvents
events={[
{
childName: "firstBar", // if a child name is not provided, event will be attached to all children.
target: "data", // what type of element to attach to. Matches the style namespaces
eventKey: 1, // What event key of element to attach to. Defaults to the index in data.
eventHandlers: {
onClick: () => {
return {
childName: "secondBar", // the child to be modified
// props here are the props that define the targeted component i.e. what is passed to an individual bar
mutation: (props) => {
return {style: merge({}, props.style, {fill: "blue"})}; // Whatever is returned here will override the existing props
}
};
}
}
}, {
childName: "secondBar",
target: "data",
eventKey: 0,
eventHandlers: {
onClick: () => { // event handlers can return an array of mutation objects with different targeted elements
return [
{
childName: "firstBar",
mutation: (props) => {
return {style: merge({}, props.style, {fill: "cyan"})};
}
}, {
mutation: (props) => { // the default target element is whatever element the handler is attached to
return {style: merge({}, props.style, {fill: "orange"})};
}
}, {
target: "labels",
eventKey: 1,
mutation: () => {
return {text: "CLICKED"};
}
}
];
}
}
}
]}
>
<VictoryBar
name="firstBar" // if children don't have name props they can be referenced by index in shared events
style={{
data: {width: 25, fill: "gold"}
}}
data={[{x: "a", y: 2}, {x: "b", y: 3}, {x: "c", y: 4}]}
/>
<VictoryBar
name="secondBar"
data={[{x: "a", y: 2}, {x: "b", y: 3}, {x: "c", y: 4}]}
/>
</VictorySharedEvents>
-
improves consistency for
labelComponent
anddataComponent
props. Replaces a custom label components 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 previous label components. 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
data
and/orlabels
keys so that these values may be applied appropriately to data and label elements respectively.
- Fixes a bug in VictoryChart, VictoryGroup and VictoryStack, which was causing null animation props to be ignored.
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
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
- Adds VictoryArea as a data type compatible with VictoryChart.
- Supports custom label components
- Upgrades all repos to lodash 4
- Remove dependency on Radium
- Many performance improvements via memoization and replacing expensive merge operations
- Ignore source maps for smaller NPM installation
- Add
npm start
andnpm test
scripts for easier contribution dev workflow - Show gzipped size for minified distribution file
- Code reorganization
- Update roadmap
- 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)}
- plotting functions via the
- 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
- Demo application now works with hot reloading.
- Application dependencies like
radium
andlodash
now live in components, not in the Builder archetype. This is a breaking change. #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
- Fix build
- Add Cumulative min and max
- Fix Firefox date issue
- Fix issue with exported
dist
file. You can now include Victory vianpmcdn
:https://npmcdn.com/victory/dist/victory.min.js
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