chore(deps): bump vicoCore from 2.0.0-alpha.6 to 2.3.0

[dependabot]

Bumps vicoCore from 2.0.0-alpha.6 to 2.3.0.
Updates com.patrykandpatrick.vico:core from 2.0.0-alpha.6 to 2.3.0

Release notes

Sourced from com.patrykandpatrick.vico:core's releases.

v2.3.0

Overview

• breaking changes: none[^1]
• addressed: #356, #465, #574, #769 comment, #1060, #1167, #1171, #1186

core

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. CartesianChart has a new markerController property, and the context parameter has been removed from the previously protected getMarkerTargets.
2. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, the existing drawUnderLayers and drawOverLayers functions have been deprecated in favor of new overloads with axisDimensions parameters, and an updateAxisDimensions function has been added.

compose

1. In connection with core change 1, rememberCartesianChart has a new markerController parameter.

multiplatform

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. rememberCartesianChart has a new markerController parameter, and the context parameter has been removed from the previously protected CartesianChart.getMarkerTargets.
2. ShapeComponent and LineComponent now support shadows; add them via the shadows parameters.
3. For simplicity, the custom Shape interface has been removed in favor of Compose’s. DashedShape remains available but now takes a Compose Shape. MarkerCorneredShape has been renamed to MarkerCornerBasedShape and takes a Compose CornerBasedShape as its base.
4. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, axisDimensions parameters have been added to drawUnderLayers and drawOverLayers, and an updateAxisDimensions function has been added.
5. An issue where the LineCartesianLayer.AreaFill implementations instantiated by single and double could misposition nonuniform Fills has been resolved.

[^1]: Excluding multiplatform, which is experimental. (It will remain available, but breaking changes are more likely.)

v2.3.0-beta.1

Overview

• breaking changes: minor

core

• In CartesianMarkerController, acceptEvent has been renamed to shouldAcceptInteraction; isMarkerVisible, to shouldShowMarker; and markedEntries, to targets.
• In CartesianMeasuringContext, isMarkerVisible is now called isMarkerShown.

multiplatform

• In CartesianMarkerController, acceptEvent has been renamed to shouldAcceptInteraction; isMarkerVisible, to shouldShowMarker; and markedEntries, to targets.
• In CartesianMeasuringContext, isMarkerVisible is now called isMarkerShown.

v2.3.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #1171, #1186

multiplatform

• ShapeComponent and LineComponent now support shadows; add them via the shadows parameters.
• An issue where the LineCartesianLayer.AreaFill implementations instantiated by single and double could misposition nonuniform Fills has been resolved.

... (truncated)

Commits

• f04e662 Update dependencies
• 73ffd63 Update version name
• 6479b8a “Bug” issue form: Update version drop-down
• e13b7da Update version from 2.3.0-alpha.3 to 2.3.0-beta.1 (#1193)
• bd6a51e Rename isMarkerVisible to isMarkerShown (#1192)
• 46de69c Refactor CartesianMarkerController: rename methods and parameters for clarity...
• 88266bb “Bug” issue form: Update version drop-down
• f573b0f Update version name
• 426b1de multiplatform: Remove Shape (#1181)
• 41a4539 Replace path.getBounds() with layerBounds in multiplatform AreaFills (#1188)
• Additional commits viewable in compare view

Updates com.patrykandpatrick.vico:views from 2.0.0-alpha.6 to 2.3.0

Release notes

Sourced from com.patrykandpatrick.vico:views's releases.

v2.3.0

Overview

• breaking changes: none[^1]
• addressed: #356, #465, #574, #769 comment, #1060, #1167, #1171, #1186

core

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. CartesianChart has a new markerController property, and the context parameter has been removed from the previously protected getMarkerTargets.
2. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, the existing drawUnderLayers and drawOverLayers functions have been deprecated in favor of new overloads with axisDimensions parameters, and an updateAxisDimensions function has been added.

compose

1. In connection with core change 1, rememberCartesianChart has a new markerController parameter.

multiplatform

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. rememberCartesianChart has a new markerController parameter, and the context parameter has been removed from the previously protected CartesianChart.getMarkerTargets.
2. ShapeComponent and LineComponent now support shadows; add them via the shadows parameters.
3. For simplicity, the custom Shape interface has been removed in favor of Compose’s. DashedShape remains available but now takes a Compose Shape. MarkerCorneredShape has been renamed to MarkerCornerBasedShape and takes a Compose CornerBasedShape as its base.
4. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, axisDimensions parameters have been added to drawUnderLayers and drawOverLayers, and an updateAxisDimensions function has been added.
5. An issue where the LineCartesianLayer.AreaFill implementations instantiated by single and double could misposition nonuniform Fills has been resolved.

[^1]: Excluding multiplatform, which is experimental. (It will remain available, but breaking changes are more likely.)

v2.3.0-beta.1

Overview

• breaking changes: minor

core

• In CartesianMarkerController, acceptEvent has been renamed to shouldAcceptInteraction; isMarkerVisible, to shouldShowMarker; and markedEntries, to targets.
• In CartesianMeasuringContext, isMarkerVisible is now called isMarkerShown.

multiplatform

• In CartesianMarkerController, acceptEvent has been renamed to shouldAcceptInteraction; isMarkerVisible, to shouldShowMarker; and markedEntries, to targets.
• In CartesianMeasuringContext, isMarkerVisible is now called isMarkerShown.

v2.3.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #1171, #1186

multiplatform

• ShapeComponent and LineComponent now support shadows; add them via the shadows parameters.
• An issue where the LineCartesianLayer.AreaFill implementations instantiated by single and double could misposition nonuniform Fills has been resolved.

... (truncated)

Commits

• f04e662 Update dependencies
• 73ffd63 Update version name
• 6479b8a “Bug” issue form: Update version drop-down
• e13b7da Update version from 2.3.0-alpha.3 to 2.3.0-beta.1 (#1193)
• bd6a51e Rename isMarkerVisible to isMarkerShown (#1192)
• 46de69c Refactor CartesianMarkerController: rename methods and parameters for clarity...
• 88266bb “Bug” issue form: Update version drop-down
• f573b0f Update version name
• 426b1de multiplatform: Remove Shape (#1181)
• 41a4539 Replace path.getBounds() with layerBounds in multiplatform AreaFills (#1188)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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]

Superseded by #292.