Dependencies to composable and access to DestinationDependenciesContainer

Before, in version 0.9.2, we could provide a DestinationDependenciesContainer to a DestinationsNavHost to provide some rudimentary dependency injection to Destinations.

It seems like this feature is no longer accessible unless I provide my own NavHostEngine due to the default enigine is creating a empty DestinationDependenciesContainer by default. Is this a conscious design decision? I looked into using the manual compose calls but that easily becomes quite messy.

[Rawa]

Sounds, good! Thank you for the help and the nice library.

[raamcosta]

I see. At the moment, I think CompositionLocal is the correct solution for you then.

// top level
val LocalNavigator = compositionLocalOf<Navigator> { error("No LocalNavigator was provided") }

// inside your Activities or every time you need to provide a different Navigator instance
CompositionLocalProvider(LocalNavigator provides myNavigator) {
    // ... Content goes here , for example your DestinationsNavHost call
    // This part of Composition will see the `myNavigator` instance
    // when accessing LocalNavigator.current
}

// then in your screens:
@Destination
@Composable
fun MyScreen(
    navigator: Navigator = LocalNavigator.current
) {
    navigator.navigate//...
}

This specific code was not tested, so take it with a grain of salt.