MVI Architecture

[Yhdista]

Has anyone experienced with MVI + Voyager + ModeView. Problem is with ViewEffect/Action (usually navigation to somewhere, show toast etc.)
using ViewEffect.collectedAsState not working correctly
and with using SideEffect or something then using Navigator is impossible as the Navigator is composable.
If somebody using MVI here, can I see your base classes?

[zakrodionov]

Just get navigator before SideEffect

val navigator = LocalNavigator.currentOrThrow

LaunchedEffect(Unit) {
    viewModel.eventFlow.collect {
        when (it) {
            NavigateToLoginFlow -> navigator.push(LoginFlow())
        }
    }
}

[Yhdista]

Thx.
As I needed general solution for base class (BaseScreen) so I did this:

val navigator = LocalNavigator.currentOrThrow

LaunchedEffect(Unit) {
    viewModel.effect.collect { effect ->
        onEffect(effect, navigator)
    }
}

open fun onEffect(effect: ViewEffect, navigator: Navigator) {}

[Alaksion]

Just retrieve your navigator and use it inside a launched effect. That's how I'm doing:
Compose view
ViewModel
UiEvent

[Yhdista]

Your Screens (steps) are connected to the same ViewModel... what if every Screen has its own ViewModel... how would parent VM listens to children VM and vice versa?

[Alaksion]

What do you mean by child ViewModels?