chore(deps): bump core from 2.0.0-alpha.6 to 2.1.0-alpha.3

[dependabot]

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

Release notes

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

v2.1.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #805

compose

• In noninteractive Compose previews—which don’t support asynchronous execution—CartesianChartHost now handles CartesianChartModelProducer communication synchronously, enabling charts to display as expected. For this to work, the consumer must also move processing to the main thread—for example, by calling runTransaction from runBlocking rather than LaunchedEffect. This should be done only for previews.

multiplatform

• In noninteractive Compose previews—which don’t support asynchronous execution—CartesianChartHost now handles CartesianChartModelProducer communication synchronously, enabling charts to display as expected. For this to work, the consumer must also move processing to the main thread—for example, by calling runTransaction from runBlocking rather than LaunchedEffect. This should be done only for previews.
• An incorrect package declaration has been amended; CartesianLayerRangeProvider is now in com.patrykandpatrick.vico.multiplatform.cartesian.data.
• The sample app has been made multiplatform. In this initial version, there are three multiplatform sample charts. However, multiplatform versions of all remaining sample charts will be introduced in upcoming updates. This process will be complete by the time Vico 2.1.0 is published.

[^1]: Excluding multiplatform, which is experimental. (It will remain available, but the API is subject to change.)

v2.1.0-alpha.2

Overview

• breaking changes: none
• addressed: #353

multiplatform

This new module provides Compose Multiplatform support. The currently supported platforms are Android and iOS, but this will be expanded. multiplatform is standalone; to use it, add only the following Vico dependency:

[versions]
vico = "2.1.0-alpha.2"
# ...
[libraries]
vico = { group = "com.patrykandpatrick.vico", name = "multiplatform", version.ref = "vico" }
...

The multiplatform API closely resembles that of compose. There are some minor differences in feature set:

• compose-m3 and compose-m2 equivalents aren’t available yet. You can replicate their functionality by creating your own MaterialTheme-based VicoTheme.
• A ComponentShader equivalent isn’t available yet. You can use ShaderBrush instead.
• ShapeComponent doesn’t support shadows yet. This is due to Compose Multiplatform’s Paint lacking shadow functionality.

A Compose Multiplatform sample app and multiplatform coverage in the guide are being worked on and will be available by the time Vico 2.1.0 is published. However, with the similarity of compose and multiplatform, most of the compose documentation applies, and you can fill in the gaps by referring to the multiplatform API reference.

multiplatform is experimental; it will remain available, but the API is subject to change. While multiplatform is Jetpack Compose–compatible, compose support continues. In the distant future, compose will be removed in favor of multiplatform, which will then be renamed to compose.

v2.1.0-alpha.1

[!WARNING]

... (truncated)

Commits

• d9a29d2 Update version name
• 4c40d39 Update dependencies
• 46c485c Make sample app multiplatform
• 9d785c0 Correct CartesianLayerRangeProvider.kt package declaration
• 8fff61b Update issue and discussion forms
• 734b115 Add previews for charts in the showcase
• ef3439c Process transaction on the main thread in Compose previews
• daa42ba Update Maven Central connection time-out
• dfdd2ad Enable Kotlin Multiplatform cross-compilation
• 465ef58 Update GitHub Actions workflows
• Additional commits viewable in compare view

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

Release notes

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

v2.1.0-alpha.3

Overview

• breaking changes: none[^1]
• addressed: #805

compose

• In noninteractive Compose previews—which don’t support asynchronous execution—CartesianChartHost now handles CartesianChartModelProducer communication synchronously, enabling charts to display as expected. For this to work, the consumer must also move processing to the main thread—for example, by calling runTransaction from runBlocking rather than LaunchedEffect. This should be done only for previews.

multiplatform

• In noninteractive Compose previews—which don’t support asynchronous execution—CartesianChartHost now handles CartesianChartModelProducer communication synchronously, enabling charts to display as expected. For this to work, the consumer must also move processing to the main thread—for example, by calling runTransaction from runBlocking rather than LaunchedEffect. This should be done only for previews.
• An incorrect package declaration has been amended; CartesianLayerRangeProvider is now in com.patrykandpatrick.vico.multiplatform.cartesian.data.
• The sample app has been made multiplatform. In this initial version, there are three multiplatform sample charts. However, multiplatform versions of all remaining sample charts will be introduced in upcoming updates. This process will be complete by the time Vico 2.1.0 is published.

[^1]: Excluding multiplatform, which is experimental. (It will remain available, but the API is subject to change.)

v2.1.0-alpha.2

Overview

• breaking changes: none
• addressed: #353

multiplatform

This new module provides Compose Multiplatform support. The currently supported platforms are Android and iOS, but this will be expanded. multiplatform is standalone; to use it, add only the following Vico dependency:

[versions]
vico = "2.1.0-alpha.2"
# ...
[libraries]
vico = { group = "com.patrykandpatrick.vico", name = "multiplatform", version.ref = "vico" }
...

The multiplatform API closely resembles that of compose. There are some minor differences in feature set:

• compose-m3 and compose-m2 equivalents aren’t available yet. You can replicate their functionality by creating your own MaterialTheme-based VicoTheme.
• A ComponentShader equivalent isn’t available yet. You can use ShaderBrush instead.
• ShapeComponent doesn’t support shadows yet. This is due to Compose Multiplatform’s Paint lacking shadow functionality.

A Compose Multiplatform sample app and multiplatform coverage in the guide are being worked on and will be available by the time Vico 2.1.0 is published. However, with the similarity of compose and multiplatform, most of the compose documentation applies, and you can fill in the gaps by referring to the multiplatform API reference.

multiplatform is experimental; it will remain available, but the API is subject to change. While multiplatform is Jetpack Compose–compatible, compose support continues. In the distant future, compose will be removed in favor of multiplatform, which will then be renamed to compose.

v2.1.0-alpha.1

[!WARNING]

... (truncated)

Commits

• d9a29d2 Update version name
• 4c40d39 Update dependencies
• 46c485c Make sample app multiplatform
• 9d785c0 Correct CartesianLayerRangeProvider.kt package declaration
• 8fff61b Update issue and discussion forms
• 734b115 Add previews for charts in the showcase
• ef3439c Process transaction on the main thread in Compose previews
• daa42ba Update Maven Central connection time-out
• dfdd2ad Enable Kotlin Multiplatform cross-compilation
• 465ef58 Update GitHub Actions workflows
• 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.