Are there any good solutions for typesafe and boilerplate fr kotlinlang #compose

Are there any good solutions for typesafe and boilerplate free Compose Navigation? 1. For specific navigation graph only a certain set of destinations (sealed class hierarchy/enums) can be passed to

navigate()

2. Pass navigation arguments (like item IDs) in a typesafe manner 3. Automatically generate the route URIs with argument placeholders 4. Easily extract the navigation arguments without additional boilerplate I'm writing extension functions and sealed class hierarchies/enums for this, but this is such a common use case that maybe someone already came up with a library (or at least someone of you has good suggestions).

Hmm, this actually looks good: https://proandroiddev.com/compose-destinations-simpler-and-safer-navigation-in-compose-with-no-compromises-74a59c6b727d

Ian Lake

08/11/2022, 4:06 PM

Yep, we had talked about Compose Destinations and how you'd want to structure your code previously: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1645595702068129?thread_ts=1645552485.247699&cid=CJLTWPH7S

Lukasz Kalnik

08/11/2022, 4:28 PM

Oh, that's a great thread! Thanks so much for the link!

Ok, so I'm using Compose Destinations and I navigate passing an argument. I'm reading the argument in the ViewModel via

savedStateHandle

. The problem is, when navigated to this screen, I have to load some data based on the passed argument. Do I get a callback when the screen is being navigated to? How can I do the initial loading based on the navigation?

Never mind, there were other problems in my code which required fixing.

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1660297449828339?thread_ts=1660297247.643039&cid=CJLTWPH7S

3 Views

#compose Join Slack