Does anyone know if the accompanist navigation libraries support combining the animated and bottom s...

# compose

[mattinger]

Does anyone know if the accompanist navigation libraries support combining the animated and bottom sheet navigators? Looking at the code would suggest so:

@ExperimentalAnimationApi
@Composable
fun rememberAnimatedNavController(
    vararg navigators: Navigator<out NavDestination>
): NavHostController {
    val animatedNavigator = remember { AnimatedComposeNavigator() }
    return rememberNavController(animatedNavigator, *navigators)
}

I assume i would pass the resolve of a rememberBottomSheetNavigator() call?

[Chrimaeon]

Have a look at https://github.com/chrimaeon/curriculumvitae/blob/main/app/src/main/java/com/cmgapps/android/curriculumvitae/MainScreen.kt

[mattinger]

thanks. i believe i can accomplish the same thing with the constructor, but this confirms what i think is the right way to do this.

[mattinger]

I hope animation gets eventually folded into the main navigation library. It seems silly to have it external when it's built into the xml based version. I know why it was done (animation was experimental)

[Ian Lake]

Animation APIs in Compose (specifically AnimatedContent) are still experimental

[Ian Lake]

But yes, the correct way to pass it into rememberAnimatedNavController , just like the docs say you should do with rememberNavController : https://google.github.io/accompanist/navigation-material/

[Ian Lake]

The += method was suggested only prior to that API existing, but isn't recommended anymore, since it is doing work on every composition vs only the once