Is there a way to remember/retain a state per item...

# compose

[ursus]

Is there a way to remember/retain a state per item in LazyColumn ? (inside item scope)

Or is the only way to keep a map of there outside the scope of items

[Pablichjenkov]

You might be interested in this:
https://saurabharora.dev/posts/per-item-viewmodels-in-compose/

[ursus]

interesting.. but essentially is just sugar for the “map outside of item scope” right?

[Winson Chiu]

In the sense that all solutions have to be that because there's no other way to do it. The key saved state in that post does shove the map handing into the framework though.

I'm not convinced having that many VMs is a good idea though, it sounds like testing/previews would be really difficult.

[Pablichjenkov]

There is another API the PinnableContainer, LocalPinnableContainer.current
Basically tells the LazyColumn not to remove the children Composables when they go off the viewport

[ursus]

my case is a mini flow of few screens within chat, and wondering if feasible, would be nice to not leave the convo