If I have a StateFlow, what is the best way to map it to another StateFlow? I get a Flow back from `...

# coroutines

[Arjan van Wieringen]

If I have a StateFlow, what is the best way to map it to another StateFlow? I get a Flow back from map, but if I want it to be a StateFlow again I need to use stateIn but then I require a scope. Or is the mapped result still a stateflow?

The usecase is I have a class that I want to expose a StateFlow which is based on another one. But if I want to use stateIn I need to do this from a coroutine. So it becomes something like this:

interface History {
    val activeLocation: StateFlow<Location>
    // ...
}

class Router<R>(
    private val history: History,
    private val routing: Routing<R>,
    private val scope: CoroutineScope
) {
    lateinit var activeRoute : StateFlow<R>
        private set

    init {
        scope.launch {
            activeRoute = history.activeLocation
                .map { location -> routing.getRoute(location) }
                .stateIn(scope)
        }
    }
}

I am not sure if this is the most optimal way of doing it... I have the feeling I am overcomplicating stuff.

[Robert Menke]

That’s how I’ve done it typically. I’m not sure you need that scope.launch though.

[Arjan van Wieringen]

Well, stateIn is suspending, so I can't start it from within init normally I suppose

[stojan]

Maybe this helps https://kotlinlang.slack.com/archives/C1CFAFJSK/p1652287040843249?thread_ts=1652287040.843249&cid=C1CFAFJSK

[Arjan van Wieringen]

That is exactly what I needed! Thanks!

[hfhbd]

Well, stateIn is not suspending if you provide an initial value. Otherwise, it have to wait until a first value, so it is suspending

[Joost Klitsie]

You should do a stateIn with the other parameters:
val myFlow = otherFlow.stateIn(scope, Eagerly, <defaultValue>

[Joost Klitsie]

so in your case:

activeRoute = history.activeLocation().map {..}.stateIn(scope, Eagerly, <defaultValue>)

[Joost Klitsie]

the whole point of stateflow is that they always have a state

[Joost Klitsie]

using lateinit is not a good solution for this (because then you are at times without a state

[Arjan van Wieringen]

@Joost Klitsie you're absolutely right. I've modified my code to this