Simple-Stack Compose Integration 0.10.0
Simple-Stack Compose Integration 0.10.0 (2023-02-23)
-
BREAKING CHANGE (recommended by @matejdro):
DefaultComposeKey.RenderComposable()no longer receives aModifier. This parameter was completely pointless, and a possible source of bugs. -
BREAKING CHANGE (recommended by @matejdro): The signature of
AnimationConfigurationand specificallyComposableTransitionhas changed, and no longer receivesfullWidthandfullHeight. This info can be accessed usingModifier.drawWithContent {}and is readily available. Also,ComposableTransitionnow receivesanimationProgressas aState<Float>, and not aFloat. UsingFloatdirectly results in excessive recompositions during animation, and is bad for performance, therefore this value must be passed lazily. This is effectively a fix for a long-lasting design issue in how animation progress had been handled, created before recomposition-related best practices on deferred read were documented. -
CHANGE (required for new features):
corenow has anapidependency onandroidx.lifecycle:lifecycle-viewmodel-compose:2.5.1to supportLocalLifecycleOwner/LocalViewModelStoreOwnerper screen. -
NEW FEATURE (added by @matejdro):
corenow supports creating aLocalLifecycleOwner/LocalViewModelStoreOwnerper screen, this change is automatically applied by updating. Please note that this means from now on, AndroidX components scope themselves to the screen, and not the Activity. If you relied on the nearestLocalViewModelStoreOwnerto be theActivity, then this is no longer the case (although in most cases, using Activity-scoped ViewModels for parameter passing typically results in stale state not being reset, and is a common source of bugs.) -
NEW FEATURE:
DefaultComposeKeynow has aopen val modifier: Modifier = Modifierwhich is passed to theScreenComposable. -
UPDATE: compileSdk 33.
-
UPDATE: simple-stack to 2.6.5, simple-stack-extensions 2.2.5.
-
UPDATE: Kotlin to 1.8.10.
-
UPDATE: Compose library versions to BOM 2023.01.00.
-
UPDATE: Compose Compiler to 1.4.3.