Using the new navigation for Compose, can I use `P...

# compose

[gsala]

Using the new navigation for Compose, can I use Parcelable arguments or is it only uri-based arguments that can be parse to primitive types?

[Gabriel]

as I understand it it's meant to be used as uri like arguments

[Gabriel]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1603915310355400?thread_ts=1603915006.355200&cid=CJLTWPH7S

[gsala]

sigh.... Thanks 👍

[Ian Lake]

Yes, that's correct

[Jordi Saumell]

I was trying without success to pass a parcelable and found this.
But then, if we need to do a simple two-screens list-detail we will need to find a way to scope an object that holds the list and lives for both screens (but not more to save memory). For simple cases this is quite cumbersome compared to just passing a parcelable

[Gabriel]

I have a list of them in the viewmodel and just get the item from that list when moving to the details screen

[Gabriel]

composable(Screen.ImageItem.route + "?imageId={imageId}") { backStackEntry ->
	val imageId = backStackEntry.arguments?.getString("imageId")
	val imageItems by viewModel.imageItems.collectAsState()
	ImageItemScreen(imageItems.first { it.id == imageId })
}

[Ian Lake]

The better thread about this, with more information on how routes should be treated re: Parcelables is https://kotlinlang.slack.com/archives/CJLTWPH7S/p1604053414451400