Yahor
02/29/2024, 1:11 PMNicolas Fortin (Univ Eiffel/UMRAE)
02/29/2024, 1:38 PMYahor
02/29/2024, 2:11 PMStylianos Gakis
02/29/2024, 4:18 PMsavedStateHandle
, does that also get retained as it should?
• What about deep link support, I saw it mentioned in the docs but I didn’t find anything in the linked sample, but I might be missing somethingkatz
02/29/2024, 5:20 PMrememberSaveable
via own saver. !WARNING! backstack stored via savable yet DATA-store logic base on storeMode and might be lost during process death, see doc, it is explaind in there
• predictive back - cant say for 100%, it uses default back handler for android, custom for jvm and nothing for iOS. We may take a look into this direction, just create featureRequest.
• all savestates rememberSavable are restored, using storeageMode = Savable
will also retain all nav args/results - see doc
• deeplink itself is about to alterate backstack, we just letting you alterate it as you want, so you free to use any kind of deeplinks logic. EG: deeplinkg smth/catalog=1&item=2. You can parese is as you want and just alterate backstack smth like
pseudocode:
navController.alterateBackStack{
clear()
add(CatalogScreen, CatalogData(id=1))
}
navController.replace(DetailScreen, DetailData(id=2))
katz
02/29/2024, 5:23 PMParcelable
data store & restore (!read instruction on how to test this beheaviour, it's at line 31 in same file)Pablichjenkov
02/29/2024, 7:51 PM