Is there a good pattern for exposing a mutablestat...

# compose

[Garret Yoder]

Is there a good pattern for exposing a mutablestatelist from an object (eg, a paginator) to the UI, but not exposing the modify methods?

eg; object retains mutablestatelist, UI sees statelist. Casting it in a get function would break the state updates, no?

[Zach Klippenstein (he/him) [MOD]]

Expose it as a List

[Zach Klippenstein (he/him) [MOD]]

SnapshotStateList implements List

[Garret Yoder]

The UI updates will still work even though the state stops before it hits compose?

[Garret Yoder]

Oh cool that does work, I really didn't think that'd work since compose wouldn't have a state list anymore.

How does that work internally then that something like a LazyColumn is still aware of the state changes, is it just re-casting it back to a state list?

[Zach Klippenstein (he/him) [MOD]]

Doesn’t need to

[Zach Klippenstein (he/him) [MOD]]

https://dev.to/zachklipp/introduction-to-the-compose-snapshot-system-19cn

[Garret Yoder]

Oh cool I've been looking for some reading on how the snapshotting works, thanks!

[Zach Klippenstein (he/him) [MOD]]

There’s a bunch of posts in that series that you might find interesting then

[Zach Klippenstein (he/him) [MOD]]

And this talk if you want to go really deep: https://www.droidcon.com/2023/07/20/opening-the-shutter-on-snapshots-2/