NavGraphArhs are visible only in "start" destination about compose-destinations HOT 6 CLOSED

Hi!

NavGraph args are a bit tricky with official Compose Navigation as well. You need the back stack entry correspondent to the nav graph to make sure you'll have the args. If you navigate directly to another graph screen that is not the start one, the args will also not be there. That's why Compose Destinations APIs return nullable type in this case.

So, this is expected and how it works with official navigation library as well. You'll need to adapt to it.

from compose-destinations.

See also here:
https://composedestinations.rafaelcosta.xyz/v2/arguments/navigation-arguments#navgraph-navigation-arguments

NAV GRAPH ARGUMENTS ARE ALWAYS NULLABLE
Navigation arguments of nav graphs are tricky. They will be present if you navigate to the graph itself (for above example, doing navigator.navigate(ProfileNavGraph(id = "some id"))) and they will not be present if you navigate to one of its destinations directly.
This is how official compose navigation works as well, Compose Destinations makes it clear by returning nullable.
If you know in your case you always navigate to the Graph, you can do requireNavGraphArgs instead which will throw an exception instead of returning nullable type.

from compose-destinations.

So i have to navigate to NavGraphs every time when i want to retrive NavGraphsArgs?
For example: I have LoginNavGraphs where i have LoginDestination(start), ForgotPasswordDestination, RegisterDestination.
App start and i navigate to LoginNavGraph (i have arguments filled) then I want to redirect user to ForgotPasswordDestination with LoginNavGraph arguments so how i can navigate to this destination with arguments?

Sorry for my english ;/

from compose-destinations.

@raamcosta can you tell me how i can do this? #633 (comment)

from compose-destinations.

You can also get a hold of the NavBackStackEntry correspondent to your NavGraph, and that one will contain all nav graph arguments.

Something like this:

destinationsNavigator.getBackStackEntry(ProfileNavGraph)?.navGraphArgs<ProfileNavGraphArgs>()

from compose-destinations.

You can also get a hold of the NavBackStackEntry correspondent to your NavGraph, and that one will contain all nav graph arguments.

Something like this:

destinationsNavigator.getBackStackEntry(ProfileNavGraph)?.navGraphArgs<ProfileNavGraphArgs>()

How about get arguments in ViewModel without pass navigator to ViewModel?

from compose-destinations.