Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

victory-voronoi

Package Overview
Dependencies
Maintainers
17
Versions
146
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

victory-voronoi - npm Package Versions

1
15

32.3.4

Diff

Changelog

Source

32.3.4 (2019-08-05)

#1361 Updates to lodash^4.17.15. Thanks @tomciopp

boygirl
published 32.3.2 •

Changelog

Source

32.3.2 (2019-07-02)

#1345 - Uses updated delaunay-find instead of d3-voronoi in VictoryVoronoiContainer

boygirl
published 32.3.1 •

Changelog

Source

32.3.1 (2019-06-28)

#1344 - update lodash #1343 - revert to d3-voronoi

boygirl
published 32.3.0 •

Changelog

Source

32.3.0 (2019-06-14)

#1322 - Replaces d3-voronoi with d3-delaunay in VictoryVoronoiContainer

#1333 - replace d3-delaunay with delaunay-find

boygirl
published 32.2.3 •

Changelog

Source

32.2.3 (2019-05-13)

#1306 - Calls eventKey functions with both datum and index

boygirl
published 32.2.2 •

Changelog

Source

32.2.2 (2019-05-03)

#1304 - renames private variables to reduce potential for conflict

boygirl
published 32.2.1 •

Changelog

Source

32.2.1 (2019-05-02)

#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

boygirl
published 32.2.0 •

Changelog

Source

32.2.0 (2019-04-10)

#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

boygirl
published 32.1.0 •

Changelog

Source

32.1.0 (2019-03-18)

#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!

boygirl
published 32.0.0 •

Changelog

Source

32.0.0 (2019-02-27)

Horizontal Chart Improvements!

#1258

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 the y value always refers to the dependent dimension.
  • the orientation of VictoryAxis components is no longer tied to whether or not they are the dependentAxis

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

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc