v9.2.0

Compare Source

v2.3.0

Overview

• breaking changes: none¹
• 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.

v9.12.2

Compare Source

[!WARNING]
If you don't have any login system in your app, please make sure your one-time purchase products have been correctly configured in the RevenueCat dashboard as either consumable or non-consumable. If they're incorrectly configured as consumables, RevenueCat will consume these purchases. This means that users won't be able to restore them from version 9.0.0 onward.
Non-consumables are products that are meant to be bought only once, for example, lifetime subscriptions.

v2.3.2

Compare Source

What's Changed

Note: This release is a hotfix for a regression introduced in 2.3.1

• Fixed an issue where KSP incorrectly processed specific nullable annotations from Java interfaces, leading to incorrect nullability in the generated Kotlin code #​2696
• Fixed a regression introduced in #​2656 that caused runtime failures for projects using AGP 8.8.0 and older due to an incompatible, version-specific type check. #​2694

Contributors

Thanks to everyone who reported bugs and participated in discussions!

Full Changelog: google/ksp@2.3.1...2.3.2