UNPKG

victory-chart

Version:

Chart Component for Victory

github.com/formidablelabs/victory-chart

formidablelabs/victory-chart

91 lines (57 loc) • 4.22 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# VictoryLine Changelog ## 8.0.0 (2016-05-13) - improves consistency for `labelComponent` and `dataComponent` props. Replaces a custom `SliceLabel` component with `VictoryLabel` to make the api more consistent and predictable. **This is a breaking change for custom label components**, as `VictoryLabel` expects a different set of props than the previous `SliceLabel` component. See [VictoryLabel](http://formidable.com/open-source/victory/docs/victory-label) 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` or `dataComponent`, 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` or `dataComponent` - it is now possible to specify `angle` and `verticalAnchor` props for` VictoryLabel` via the style object - event return values are stored differently on state to facilitate interaction between data and labels. **This is a breaking change for events** as event handlers must now return an object with with `data` and/or `labels` keys so that these values may be applied appropriately to data and label elements respectively. ## 7.0.0 (2016-04-15) - VictoryBar and VictoryArea no longer support multiple datasets. - VictoryStack and VictoryGroup define stacked and grouped layouts for their children - Custom data components supported on for VictoryBar, VictoryLine, VictoryScatter, VictoryArea via the `dataComponent` prop - Enter and exit transitions animate. Enter and exit transition defaults defined VictoryBar, VictoryArea, VictoryScatter, and VictoryLine. Custom transitions may be defined via the `onExit` and `onEnter` properties of the `animation` 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 ## 6.0.0 (2016-03-14) - Add VictoryArea component - Add event handling via an `events` prop - Update to lodash 4 - Update `d3-shape` to the latest version (minor breaking changes on interpolation types) - Updates via `builder-victory-component` to support Babel 6 - Provide label text via a `text` prop rather than children ## 5.0.2 (2016-03-04) - Add validation of length for `dataAttributes` prop - Remove source-maps from git - Various documentation fixes ## 5.0.1 (2016-03-01) - Provide datum to victory-line custom label - Upgrade to `victory-core@1.0.0` ## 5.0.0 (2016-02-26) - VictoryBar, VictoryLine, VictoryScatter, and VictoryAxis are now all part of the VictoryChart repo. - VictoryChart depends on VictoryCore instead of VictoryUtil, VictoryLabel, and VictoryAnimation individually. - VictoryChart no longer depends on Radium - Significant rendering performance improvements ## 4.0.0 (2016-01-30) - Supports data accessor functions! [more detail](https://github.com/FormidableLabs/victory/issues/84) - Application dependencies like `radium` and `lodash` now live in components, not in the Builder archetype. This is a breaking change. https://github.com/FormidableLabs/victory/issues/176 ## 3.0.0 (2016-01-26) - 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 ## 2.2.0 (2016-1-21) - Extracted shared code into `victory-util` - Increased unit test coverage to ~75% ## 2.1.3 (2015-12-30) - update archetype ## 2.1.2 (2015-12-30) - Fixed a bug in `victory-bar` that was causing the cumulative max on stacked bar charts to be overestimated - Fixed a bug related to date formatting in Firefox ## 2.1.1 Alpha (2015-12-18) Functional styles and functional props (where appropriate) for child components using `d3-modules` instead of all of `d3` Basic code coverage. We make no promises about any code prior to this release.