Why does experimental.ChildStack use experimental.stack.animation.StackAnimationer instead of StackAnimation

[BryanSer]

Hello,
I have a question regarding the animation handling in the experimental ChildStack composable.
I noticed that com.arkivanov.decompose.extensions.compose.experimental.stack.ChildStack accepts a com.arkivanov.decompose.extensions.compose.experimental.stack.animation.StackAnimationer for animations.
However, there is also a non-experimental com.arkivanov.decompose.extensions.compose.stack.animation.StackAnimation.
I am curious about the design decision behind this. Why was the new experimental StackAnimationer introduced for the experimental ChildStack instead of reusing the existing StackAnimation?
Are there plans for StackAnimationer to eventually replace StackAnimation, or do they serve different purposes?

[arkivanov]

Hello,

There is no such thing as StackAnimationer, the new ChildStack composable function accepts StackAnimation. The new API was introduced to support AnimatedVisibilityScope (now it's StackAnimationScope), which is required for shared transitions.

The new API will completely replace the old one in the next major release (4.x).