at the moment i am doing: ``` @Composable private fun configureNavigation() { val navControll...

# koin

[Moritz Post]

at the moment i am doing:

@Composable
  private fun configureNavigation() {
    val navController = rememberNavController()
    loadKoinModules(module { single<NavController> { navController } })
  }

This has the disadvantage that i have to actively unload the module when the Activity is destroyed.

[Giorgos Neokleous]

Why do you need to load it into a module and provide it as singleton? rememberNavController should be enough. Internally it uses compose's remember https://developer.android.com/jetpack/compose/navigation#getting-started

[Moritz Post]

That is correct but you have to use composable functions inside another composable function.

[Moritz Post]

so you can not use remberNavController() in your module declaration

[Giorgos Neokleous]

Yeah but my question is why do you need to do that?

[Giorgos Neokleous]

You should create the NavController in the place in your composable hierarchy where all composables that need to reference it have access to it.

From the link I've sent. I don't think there is a reason to injected with Koin. You can pass it as a method argument

[Moritz Post]

That is correct as well. In some cases you might need to be pass it pretty far down the compose node chain.

[Moritz Post]

another option could be to make it a Compose ambient