For a custom data type we should override one more function in the NavType to avoid that run-time exception: serializeAsValue() and just return Json.encodeToString(value) ✅
You always find amazingly good content. Thanks for the effort you put into teaching us something new. My day is perfect when it starts with your videos. Thank you.
I always use a navigation viewModel to hold the data( also complex objects) and then read it from the destination screen. Use enum classes to define routes to overcome typing errors. This approach with compose navigation works well in every scenario.
Currently I'm taking Your course on Udemy ToDo App with Compose, and these string-based routes were strange to me. What a perfect time for this video to come out 😅
Bro still basic ui components are (Experimental) and has bugs for 3 year still they dont care it ? And why they still making shitshow apis intead of fix experimentals and stable it. Imagine getting type safe arguments after 3 years.I really dont understand them
Isnt it more convenient to convert custom object to Jsonstring and pass as string param then parse the 'Json to object instead of creating navtype boilerplate code? Pass Gson().toJson(yourModelClassObject) in string param, then for getting it use generic function: inline fun String?.parseJsonString(): T? { return try { this?.let { val type = object : TypeToken() {}.type Gson().fromJson(it, type) } } catch (e: JsonSyntaxException) { Log.i("Error", "Failed to parse JSON string: ${e.message}") null } } val screenA = it.toRoute() val data = screenA .jsonstring.parseJsonString()
For a custom data type we should override one more function in the NavType to avoid that run-time exception: serializeAsValue() and just return Json.encodeToString(value) ✅
Wow ita great to see such features. Anyways i wish they could make similar implementation like voyager in jepack naviagation which is so easy to do.🥰
@galaxiegalaxie5003 Oh yeah Voyager has a really nice API indeed 😊
You always find amazingly good content. Thanks for the effort you put into teaching us something new. My day is perfect when it starts with your videos. Thank you.
I'll wait to see the stable one, this is really amazing
I always use a navigation viewModel to hold the data( also complex objects) and then read it from the destination screen.
Use enum classes to define routes to overcome typing errors.
This approach with compose navigation works well in every scenario.
Bro I'm new to compose.can u provide any links to learn navigation
your video is amazing. Thank you so much for sharing this new technology with us.
can't wait to test it out. it's been a long time especially because we already have type-safe in xml navigation
me too !
finally!!!! it was a giant pain in the ass for me! it's time for refactoring!!
Thanks you for the video my friend.
Nice update ✌
Currently I'm taking Your course on Udemy ToDo App with Compose, and these string-based routes were strange to me. What a perfect time for this video to come out 😅
I'll also update the course with this new approach, I'm waiting for a beta release just in case. :)
Can you make a video about explaining all the effects (like LaunchEffect and all)
They are adding @Serializable and @Parcelable both to a class ? i was under impression parcelable can improve app performance over serilization.
The new safe args navigation doesn't seem to work with deeplink.😢
Can we still get runtime args from SavedStateHandle in viewmodels?
it's also work with Parcelize ?
Wow 🎉
I tried and faced the similar crash.
Can you access the argument in the viewmodel?
Yes, you can use SavedStateHandle and call the same toRoute() function within the ViewModel.
1:38 Is it possible to replace its sealed class Screen with a sealed interface Screen?
Haven't used sealed interface that much at all.
Can you say what the better this navigation or voyager
Ah, you're asking hard questions 😄
@@StevdzaSan😄
I suggest you change the title of your video to include words navigation so its easier to find later!
Thanks for the tip!
eventually :)
Bro still basic ui components are (Experimental) and has bugs for 3 year still they dont care it ? And why they still making shitshow apis intead of fix experimentals and stable it. Imagine getting type safe arguments after 3 years.I really dont understand them
Bugs are gonna be always present. I've never had any issue with their basic components. On what exactly are you referring to?
@@StevdzaSan e.g. disable swipe on bottomsheet. Put scrollable layout in it .bottomSheet closing on swipe. m3
Try flutter and make difference video
first
Isnt it more convenient to convert custom object to Jsonstring and pass as string param then parse the 'Json to object instead of creating navtype boilerplate code?
Pass Gson().toJson(yourModelClassObject) in string param, then for getting it use generic function:
inline fun String?.parseJsonString(): T? {
return try {
this?.let {
val type = object : TypeToken() {}.type
Gson().fromJson(it, type)
}
} catch (e: JsonSyntaxException) {
Log.i("Error", "Failed to parse JSON string: ${e.message}")
null
}
}
val screenA = it.toRoute()
val data =
screenA .jsonstring.parseJsonString()