If I have a `MutableState`, I can expose it as rea...

# compose

[Dominik Seemayr]

If I have a MutableState, I can expose it as read-only value to other classes as State<String>, just like:

private val _title = mutableStateOf("abc")
val title: State<String> = _title

Is there a way to do this with SnapshotStateList<> too? How would I do this for example with:

private val _titles = mutableStateListOf<String>(...)
val titles: ??? = _titles

[Albert Chang]

val titles: List<String>
    get() = _titles

[Albert Chang]

Also the MutableState case can be simplified to:

var title by mutableStateOf("abc")
    private set

[Dominik Seemayr]

Thanks @Albert Chang! Tho, if a composable would use this titles variable, would it be recomposed when _titles changes? Since it's not aware of a State object, but just a List<String>. Or is compose smart enough for that?

[Albert Chang]

Yep. Indirect read of the state will also work.

[Dominik Seemayr]

thanks man :))

[Colton Idle]

Is this a common pattern? I remember following this backing property pattern for live data but I haven't done it with compose and it seems to be no worse off.

[Dominik Seemayr]

@Colton Idle i think the way @Albert Chang wrote it is the way you should do it (with private set) for basic states

[tad]

It depends on when you want the read to happen. State<T> allows consumers to obtain the state holder without performing a read, while var ... by mutableStateOf(...) forces a read when the field is accessed.