victory-line - npm Package Versions

30.2.0 (2018-08-06)

• #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 and candleWidth props to VictoryBar and VictoryCandlestick. Adds candleRatio prop to VictoryCandlestick
• #1079 Adds onBrushCleared callback prop for VictoryBrushContainer
• #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)

30.1.0 (2018-07-27)

-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 or id prop. -1063 Makes prop-types a real dependency

30.0.0 (2018-07-17)

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 renamed LineSegment
• Victory no longer supports git installs
• victory-chart and victory-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
• victory-axis@30.0.0 exports VictoryAxis
• victory-area@30.0.0 exports VictoryArea and Area
• victory-bar@30.0.0 exports VictoryBar and Bar
• victory-box-plot@30.0.0 exports VictoryBoxPlot
• victory-brush-container@30.0.0 exports VictoryBrushContainer, BrushHelpers and brushContainerMixin
• victory-brush-line@30.0.0 exports VictoryBrushLine
• victory-candlestick@30.0.0 exports VictoryCandlestick and Candle
• victory-chart@30.0.0 exports VictoryChart
• victory-core@30.0.0 still exports several packages that are used by several Victory components:
  • VictoryAnimation
  • VictoryClipContainer
  • VictoryContainer
  • VictoryLabel
  • VictoryPortal and Portal
  • VictoryTheme
  • VictoryTransition
  • Several primitive components: Arc, Border / Box, Circle, ClipPath, LineSegment (formerly Axis / 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
• victory-create-container@30.0.0 exports createContainer, combineContainerMixins and makeCreateContainerFunction
• victory-cursor-container@30.0.0 exports VictoryCursorContainer, CursorHelpers and cursorContainerMixin
• victory-errorbar@30.0.0 exports VictoryErrorBar and ErrorBar
• victory-group@30.0.0 exports VictoryGroup
• victory-legend@30.0.0 exports VictoryLegend
• victory-line@30.0.0 exports VictoryLine and Curve
• victory-pie@30.0.0 exports VictoryPie and Slice
• victory-scatter@30.0.0 exports VictoryScatter
• victory-selection-container@30.0.0 exports VictorySelectionContainer, SelectionHelpers and selectionContainerMixin
• victory-shared-events@30.0.0 exports VictorySharedEvents
• victory-stack@30.0.0 exports VictoryStack
• victory-tooltip@30.0.0 exports VictoryTooltip and Flyout
• victory-voronoi@30.0.0 exports VictoryVoronoi and Voronoi
• victory-voronoi-container@30.0.0 exports VictoryVoronoiContainer, VoronoiHelpers and voronoiContainerMixin
• victory-zoom-container@30.0.0 exports VictoryZoomContainer, RawZoomHelpers, ZoomHelpers and zoomContainerMixin

31.0.0 (2018-11-10)

• #1177 Adds support for controlling radius, innerRadius, cornerRadius, padAngle, sliceStartAngle and sliceEndAngle 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.

0.8.0 (2016-06-01)

• 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>

0.7.0 (2016-05-13)

• improves consistency for labelComponent and dataComponent props. Replaces a custom label components 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 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 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 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/or labels keys so that these values may be applied appropriately to data and label elements respectively.

0.6.0 (2016-04-15)

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