Releases: FormidableLabs/victory
35.8.1
35.8.0
(2021-05-19)
- #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.
v35.7.2
35.7.1
35.7.0
(2021-05-12)
- #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!
35.6.4
35.6.3
35.6.2
35.6.1
35.6.0
(2021-05-04)
- #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!