what is the right way to "bubble up" the callback for a navigation in a nested graph? I have someth...

# compose

[mgrazianodecastro]

what is the right way to "bubble up" the callback for a navigation in a nested graph?

I have something like:

---> A (with public children x)
Main --/
       \---> B

and I need to pass the callback access to children x. What's I've tried is to create it inside the A module, like so:

fun NavController.navigateToX(arg: String){
    val destination = [e-mail] + "/" + arg
    navigate(destination)
}

but when I access it through Main into the B module, it doesn't find the route. Should I append more things at the beginning?

[mgrazianodecastro]

I've also added NAV_GRAPH_ROUTE + / + ... to see if it works, but without success

[Matt Rea]

Each feature should create an extension on NavGraphBuilder, then call each feature from the root graph

Then just pass in a lambda to navigate

fun NavGraphBuilder.featureA(navigateToX: (String) -> Unit)

[mgrazianodecastro]

that's how I've been doing, but no success

[mgrazianodecastro]

lemme double check if I'm not doing something weird with strings (lol)

[mgrazianodecastro]

Yep, I was doing something weird with the strings. Our solution works