this is how all this videos should have been made. no bs corporate music, no apple style excitement, no weird acting. just a normal person sharing her knowledge. please only do this way, don't be annoying. please.
Shiny new API...but is there any migration path for old XML based apps ...or multi module apps where all you can do is adding hacks or stick to deep links usage
I have just experimented with NavType. It doesn't support to have a class in another class. For example: @Serializable data class Profile(val settings: Setting, val name: String), @Serializable Setting(val name: String). It didn't work
I found it! Here is how: composable { navBackStackEntry -> val parameter= remember(navBackStackEntry) { navController.getBackStackEntry() .toRoute().parameter } ... ) }
@@TheMikkelet Can't post a link, but try to recreate the code from the Custom Types section where the "Search" navigation route parameter type is the "SearchParameters" data class.
Subscribe for the latest updates → goo.gle/AndroidDevs
this is how all this videos should have been made. no bs corporate music, no apple style excitement, no weird acting. just a normal person sharing her knowledge. please only do this way, don't be annoying. please.
I was going to say the same. So just echoing what you said. Awesome. Many thanks to the presenter (and whomever prepared this crystal clear video).
agreed
Actually, as an iOS dev, this very Apple style and I like it
it also helps that the speaker isnt some bulgarian 47 year old with an ielts speaking score of 2.5
untapped voice talent
Thank you for great content. Can you also give an example for how to return a result to previous destination ?
Hay từ giọng nói cho đến nội dung.
From Việt Nam with love 🇻🇳🇻🇳🇻🇳
very helpful, the previous implementation was a nightmare for complex data to pass
Could please specify where you put BotttomNavigation? Is it in Scaffold, that wraps all NavHost?
Nice explanation, very relaxing too
this was by far the best informative video from this channel looking forward to see more videos from Clara
Waiting for stable release for type safe navigation in compose nav since 2.8.0-alpha08, Now it is stable Voila!
Clear explanation. Thanks.
Thanks, it's really convenient (well, maybe except the decision to deal with path in deep links, which may be controversial)
Best video and best presenter till date loved the content loved the presentation. Please bring her with more topics ❤❤❤
Really nice and simple explanation
This is very important!
Helpful
Shiny new API...but is there any migration path for old XML based apps ...or multi module apps where all you can do is adding hacks or stick to deep links usage
I have just experimented with NavType. It doesn't support to have a class in another class. For example: @Serializable data class Profile(val settings: Setting, val name: String), @Serializable Setting(val name: String). It didn't work
how about a navgraphbuilder with SharedTransitionScope composables?
Subscribed!
about time
Hello, how can I navigate to a navigation graph with parameter and pass it to the startDestination?
I found it!
Here is how:
composable { navBackStackEntry ->
val parameter= remember(navBackStackEntry) {
navController.getBackStackEntry()
.toRoute().parameter
}
...
)
}
Why aren't they using kotlin-parcelize ?
Google is preparing navigation library as a KMP(Kotlin Multiplatform) solution, so it shouldn't contain any android-related components
@@龔詩測試機1號 ohh I see. Thanks 👍🏼
Funny that they knew that removing type safety was a bad thing still they went ahead with it and now had to bring in the type safety back.
What if I want to pass another data class as parameter? Like `data class LogginId(profile: Profile)`
Use the link "Navigation Compose meet Type Safety blog" in the video description. There is a section that called "Custom types".
@@carrie5230 Keep getting "Navigation destination that matches request cannot be found in nav graph" error
@@TheMikkelet Can't post a link, but try to recreate the code from the Custom Types section where the "Search" navigation route parameter type is the "SearchParameters" data class.
The docs cover how to add custom NavTypes
Put it in a view model that both composables can access so you don't have to worry about type safety
is she AI or ready to be replaced by AI?
I was expecting your comment. I guess AI also can replace the comment field ;)
I am not buying it. Got ps5 slim with disc. Happy with it