@Arkadii Ivanov the latest version has a new stateflow to observe state. Do you have a sample how we can use it ???

No, as far as I know. But this should be essentially the same as with usual

state.states

.

so we do not need use

Value<out T : Any>

anymore

I mean you can use the new API, or you can continue using Value. MVIKotlin can be used without Decompose. 😀

ok. I want use the new API together with Decompose.

interface ScanComponent {
    val states: Flow<ScanStore.State>
}

class ScanComponentImpl {
    override val states: StateFlow<ScanStore.State> = store.stateFlow
}

And in the UI a call

val uistate by component.states.collectAsState(null)

. Everything works like a charm but the collectAsState need for initial state and the

uistate

can be null. The store has an initial state, so it is interesting collectAsState to wait the store emit the first state. Do you have some idea???

I think you need to use StateFlow in your ScanComponent interface.

You are right as always

Also please be aware of this possible trap - https://kotlinlang.slack.com/archives/C01403U1ZGW/p1672414132375969?thread_ts=1672414132.375969&cid=C01403U1ZGW