Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
victory-zoom-container
Advanced tools
victory-zoom-container@^30.0.0
exports VictoryZoomContainer
, zoomContainerMixin
, ZoomHelpers
, and RawZoomHelpers
View these docs at https://formidable.com/open-source/victory/docs/victory-zoom-container to see live examples.
VictoryZoomContainer
provides pan and zoom behavior for any Victory component that works with an
x, y axis. Zoom events are controlled by scrolling, and panning events are controlled by dragging.
See an example of a zoomable chart
VictoryZoomContainer
may be used with any Victory component that works with an x-y coordinate
system, and should be added as the containerComponent
of the top-level component. However, the component that uses it must be standalone
(standalone={true}
), which is the default for all top-level Victory components.
<VictoryChart domainPadding={{ y: 10 }}
containerComponent={
<VictoryZoomContainer/>
}
>
<VictoryScatter
y={(datum) => Math.sin(2 * Math.PI * datum.x)}
/>
</VictoryChart>
VictoryZoomContainer
uses a superset of props used by VictoryContainer. All props are optional.
type: boolean
The optional allowPan
prop accepts a boolean that enables the panning functionality. Zooming will still be enabled when the allowPan
prop is set to false.
default: allowPan={true}
type: boolean
The optional allowZoom
prop accepts a boolean that enables the zoom functionality. Panning will still be enabled when the allowZoom
prop is set to false.
default: allowZoom={true}
type: element
VictoryZoomContainer
works by clipping data outside of a given domain. VictoryZoomContainer
uses VictoryClipContainer
by default. This prop should not be replaced with a custom component, but you may want to set props on VictoryClipContainer
, such as clipPadding
example: clipContainerComponent={<VictoryClipContainer clipPadding={{top: 10, right: 10}}}/>}
type: boolean
When the disable
prop is set to true
, VictoryZoomContainer
events will not fire.
type: number || boolean
The downsample
prop limits the number of points that will be displayed. This prop may be given as a boolean or a number corresponding to maximum number of points. When given as a boolean, the maximum number of points that will be plotted is 150.
type: { x: number, y: number }
The minimumZoom
prop sets a minimum domain extent for the zoomed chart. When the difference between
the maximum and minimum of a zoomed domain is equal to the minimumZoom
in either dimension, the
component will stop responding to events that would normally trigger zooming in. Zooming out and
panning will still be enabled. When this prop is not specified, the default minimum zoom will
cover 1 / 1000th of the original domain. This prop should be given as an object with numeric values
for x and y.
example: minimumZoom={{x: 1, y: 0.01}}
type: function
The optional onZoomDomainChange
prop accepts an function to be called on each update to the visible domain. The function accepts the parameters domain
(the updated domain) and props
(the props used by VictoryZoomContainer
).
example: onZoomDomainChange={(domain, props) => handleDomainChange(domain, props)}
type: { x: [low, high], y: [low, high] }
The zoomDomain
prop describes the zoomed state. This prop is an object that
specifies separate arrays for x and y. Each array is a tuple that describes the minimum and maximum
values to render. If this prop is not provided initially, the chart will render without an initial
zoom, displaying the entire dataset. Updates to zoomDomain
will trigger a re-render of the chart
with the new domain.
example: zoomDomain={{x: [0, 100]}}
type: "x" || "y"
When the zoomDimension
prop is set, panning and zooming will be restricted to the given dimension
(either x or y), and the domain of the other dimension will remain static. When this prop is not
specified, both x and y dimensions will pan and zoom.
example: zoomDimension="x"
31.1.0 (2019-01-08)
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 like x="_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 the animate
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.
FAQs
Interactive Zoom Component for Victory
The npm package victory-zoom-container receives a total of 93,958 weekly downloads. As such, victory-zoom-container popularity was classified as popular.
We found that victory-zoom-container demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 16 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.