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

[dependabot]

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

Release notes

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

v2.4.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #1202, #1203, #1221

core

• The x-values of CartesianMarkers are no longer clamped to the visible x-range.
• In MeasuringContext, canvasBounds has been deprecated in favor of canvasSize; see the deprecation message for more.
• In CartesianMeasuringContext, pointerPosition and isMarkerShown have been deprecated in favor of markerX; see the deprecation messages for more.
• In CartesianChart, the existing getMarkerTargets overload has been deprecated in favor of a new one, with x and visibleXRange parameters.

compose

• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.

views

• An issue where CartesianChartView mishandled padding, leading to incorrect CartesianChart rendering and Bitmap-related crashes, has been resolved.
• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.

multiplatform

• The x-values of CartesianMarkers are no longer clamped to the visible x-range.
• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.
• In CartesianMeasuringContext, pointerPosition and isMarkerShown have been removed in favor of markerX; use markerX and markerX != null, respectively.
• In CartesianChart, getMarkerTargets now has x and visibleXRange parameters.

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

v2.4.0-alpha.2

Overview

• breaking changes: none
• addressed: #1217

compose

• CartesianChartHost has been updated to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.

multiplatform

• CartesianChartHost has been updated to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.

v2.4.0-alpha.1

Overview

• breaking changes: none
• addressed: #1115

... (truncated)

Commits

• 7b26ffd Update version name
• 8f683d3 Use rememberSaveable for chartID in ChartScreen (#1228)
• 0b0b196 Refactor: Use x-axis value for marker target retrieval (#1227)
• 7dbad8b Fix CartesianChartView mishandling padding (#1223)
• 8706790 Fix deprecation message format: Drawable#getOpacity → Drawable.getOpacity (#1...
• 6699aaa “Bug” issue form: Update version drop-down
• 6a737af Update version name
• 2583e24 Replace fixed height with max height constraint in CartesianChartHostBox (#1219)
• 4fd9e3a Update issue and discussion forms
• bf8f6d0 Update version name
• Additional commits viewable in compare view

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

Release notes

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

v2.4.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #1202, #1203, #1221

core

• The x-values of CartesianMarkers are no longer clamped to the visible x-range.
• In MeasuringContext, canvasBounds has been deprecated in favor of canvasSize; see the deprecation message for more.
• In CartesianMeasuringContext, pointerPosition and isMarkerShown have been deprecated in favor of markerX; see the deprecation messages for more.
• In CartesianChart, the existing getMarkerTargets overload has been deprecated in favor of a new one, with x and visibleXRange parameters.

compose

• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.

views

• An issue where CartesianChartView mishandled padding, leading to incorrect CartesianChart rendering and Bitmap-related crashes, has been resolved.
• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.

multiplatform

• The x-values of CartesianMarkers are no longer clamped to the visible x-range.
• An issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized has been resolved.
• In CartesianMeasuringContext, pointerPosition and isMarkerShown have been removed in favor of markerX; use markerX and markerX != null, respectively.
• In CartesianChart, getMarkerTargets now has x and visibleXRange parameters.

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

v2.4.0-alpha.2

Overview

• breaking changes: none
• addressed: #1217

compose

• CartesianChartHost has been updated to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.

multiplatform

• CartesianChartHost has been updated to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.

v2.4.0-alpha.1

Overview

• breaking changes: none
• addressed: #1115

... (truncated)

Commits

• 7b26ffd Update version name
• 8f683d3 Use rememberSaveable for chartID in ChartScreen (#1228)
• 0b0b196 Refactor: Use x-axis value for marker target retrieval (#1227)
• 7dbad8b Fix CartesianChartView mishandling padding (#1223)
• 8706790 Fix deprecation message format: Drawable#getOpacity → Drawable.getOpacity (#1...
• 6699aaa “Bug” issue form: Update version drop-down
• 6a737af Update version name
• 2583e24 Replace fixed height with max height constraint in CartesianChartHostBox (#1219)
• 4fd9e3a Update issue and discussion forms
• bf8f6d0 Update version name
• 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]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.