Bump apexcharts from 7.1.0 to 7.2.0 in /react

[dependabot]

Bumps apexcharts from 7.1.0 to 7.2.0.

Release notes

Sourced from apexcharts's releases.

💎 Version 7.2.0

A minor release built around the plugin layer and one new look for an existing type. Weave, the plugin host, gets two contract revisions: v2 hands a plugin enough context to decide whether it applies, and v3 lets one ask the chart for room to draw its own UI. Heatmap cells can now be hexagons, circles or diamonds, with a honeycomb tilemap that tessellates properly rather than approximating one.

Alongside that, eleven fixes. Six came from outside contributors, and they cluster on the parts of the library that are hardest to get right from the inside: stacked combo charts, brush selection bounds, annotation clamping and grouped tooltips.

	gzip
7.1.0 default bundle	264,308 B
7.2.0 default bundle	266,813 B

No API breaking changes. There is one deliberate behaviour change, described in the first fix below: a series the viewer switched off in the legend now stays off across a data update. Upgrading is npm install apexcharts@7.2.0.

✨ New

Heatmap cell shapes

plotOptions.heatmap.shape takes 'rect' (the default), 'hexagon', 'circle' or 'diamond'.

new ApexCharts(el, {
  chart: { type: 'heatmap' },
  plotOptions: { heatmap: { shape: 'hexagon' } },
  series: [/* ... */],
}).render()

'circle' and 'diamond' are inscribed in the cell box the heatmap already lays out. 'hexagon' is a real honeycomb: pointy-top hexagons stretched to the cell width and 4/3 of the row pitch tall, with alternate rows offset a quarter cell so every neighbouring pair shares a full edge. The lattice overhangs the grid, so that overhang is reserved as a grid-padding floor and the heatmap group gets its own widened clip; offset rows never slide under the y-axis labels and nothing is sliced at the edges.

Shaped cells render as SVG paths that keep the apexcharts-heatmap-rect class and the same attribute contract, so tooltips, keyboard navigation, legend range highlighting and the color tween on a data update all work unchanged. Corner radius applies to 'rect' only, hexagon falls back to 'rect' on a numeric or datetime x axis, and the canvas renderer declines non-rect shapes the same way it declines image fills.

Weave plugin API v2

Two fixes and four additions to the plugin host (import 'apexcharts/features/weave', included in the default bundle).

Every Weave plugin silently did nothing on a pie, donut or radialBar. Those charts hold one number per entry rather than a row of values, and the data snapshot called .map on it; the per-plugin guard caught the exception and disabled the plugin, so the failure looked like the plugin's fault. Each slice is now presented as a one-point series. Separately, the version gate demanded an exact match, so the first additive change to the contract would have disabled every plugin already written against v1. It is now forward-compatible: an older plugin is served, and only one needing a newer host than this is skipped.

Added in v2:

• data[].raw: the caller's own data array, untouched by parsing. The normalised points are fine to read and wrong to copy, since the three accepted shapes are not interchangeable.
• info: chart type, axis kind, horizontal bars and the data-label config, so a plugin can decide whether it applies instead of adding a series and letting the core warn at the user.
• categories: display labels resolved config-first. Reading globals.categoryLabels directly gave real labels on first paint and ordinals after an updateSeries.
• markDerived(names): a plugin declares which series are its own, and the host keeps them out of the initial-series snapshot. Without it, resetSeries() hands the user a plugin's computed output as if it were their own data.

Weave plugin API v3: reserving container space

A plugin that renders its own HTML beside the chart (a docked panel, its own toolbar) had no good way to make room for it. The chart sizes itself from the container it was handed, so a sibling inserted into that container does not narrow the chart, it gets drawn at full width underneath it.

api.reserve({ right: 220 })  // null gives the space back

... (truncated)

Commits

• 5f5f2f7 release: 7.2.0
• 78bfc9e chore: bump version to 7.2.0
• 2d0f6e8 feat(weave): let a plugin reserve container space for its own UI
• 27d89c3 fix(weave): project charts the host lays out in bands
• 2d67958 fix(series): keep legend collapses across a data update
• 62781f7 build(deps): take apex-commons 0.7.0
• bb4a333 chore: build against the current apex-commons
• 2110bd3 fix(weave): make api.scales layer-local so plugin drawings land on the data
• 2fcb738 release: 7.2.0-rc.2
• 105074d chore: bump version to 7.2.0-rc.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like apexcharts is up-to-date now, so this is no longer needed.