IssueTracker

Component used: navigation-compose Version used: 2.8.1 Devices/Android versions reproduced on:

We have a nav graph with multiple routes. Each destination is represented by a serializable data object (based on recent type safety updates). While this works, the boiler plate setup code has to be repeated for every new screen.

NavHost(
navController = navController,
modifier = modifier,
startDestination = Home
) {
    composable<Home> {
        Home { screen ->
            navController.navigate(screen)
        }
    }
    composable<Displays> {
        Displays()
    }
    composable<AudioInfo> {
        AudioInfo()
    }
    composable<MediaSessions> {
        MediaSessions()
    }
    composable<Recomposition> {
        CounterDebug()
    }
    composable<CommonFlavorOverride> {
        CommonFlavorText()
    }
    composable<RotateAnimation>() {
        RotatingBox()
    }
}

It would be nice if we could just configure new destination without having to repeat the nav graph setup code.

data class Screen(
    val destination: Any,
    val content: @Composable AnimatedContentScope.(NavBackStackEntry) -> Unit
)

val composeScreens = listOf(
    Screen(Displays, { Displays() } ),
    ...
)

However, we can't loop through this composeScreens data structure in nav graph as the destination is compile time type specification. It would be nice to support a version of composable() that takes Any as a parameter as well. If not, is there any way to avoid this repetitive code?