In `navigation-compose` `1.0.0-x` I was able to pass `Parcelable` argument this way: ```currentBackS...

# compose

[pawegio]

In navigation-compose 1.0.0-x I was able to pass Parcelable argument this way:

currentBackStackEntry?.arguments?.putParcelable(...)

after updating to 2.4.0-alpha01 it seems to no longer work as I see that previousBackStackEntry?.arguments?.getParcelable returns a null value in new destination. What’s the right/new way to perform it now?

[Ian Lake]

There's about 100 threads here that say you shouldn't be trying to do this pattern in the first place. We even specifically talk about how this is an anti-pattern and absolutely the wrong thing to do in our latest video:

https://youtu.be/0z_dwBGQQWQ▾

[pawegio]

Thank, I see the point now. I somehow missed those threads.

[pawegio]

I thought that my case is exceptional as I don’t just select item from the list exposed in state, but now I understand that I need a cache.

[Javier]

@Ian Lake what do you think about inline/value classes for this? The problem with them is they are not working with parcelize, but passing typed arguments, for example instead of passing an string passing a UserId is like how web works but even better because you have typed args so you can't fail passing an incorrect argument. Obviously the idea is passing one property arguments, not creating a huge class.

What problems can have this approach (if parcelize fix the issue and this can be done)?