Question : Multiple DestinationsNavHost handling about compose-destinations

[raamcosta]

Hi @MichaelOliveiraBx

It works, but when we have more than 40 Destination, it's starting to become difficult to maintain

You can just do

dependency(OpenFullScreen { openFullScreen.invoke() })

And that will make it available to any destination in this DestinationsNavHost, even if you have a thousand. I also like how you're just passing a specific functionality you need rather than passing a whole NavController. I would go with that if possible.

I see the idea with the registry, but I would personally avoid doing this as much as possible, unless it's the only way. But if you have it and it works for you, nothing against it either :)

[WildOrangutan]

We're using CompositionLocalProvider to obtain the instance of root DestinationsNavigator.

[MichaelOliveiraBx]

Yes nice idea, I don’t think about using CompositionLocalProvider enough.
But I think I prefer in this case, to create another DestinationsNavigator and inject it with the dependency builder.
To have it directly in the destination arguments

[MichaelOliveiraBx]

Hi 👋
Yes ok I see, I know that the interface is available in all destination, we can continue to use the dependency but be more smart, I will make an interface to navigate to all full screen destination

fun interface OpenFullScreen {
    fun invoke(destination: Destination)
}

I agree with you, I am not fan to pass whole NavController
Thanks for your feed back :)