```combine flowOne flowTwo flowThree flowThree gt flowThree

Question

```combine flowOne flowTwo flowThree flowThree gt flowThree stateIn viewModelScope + ioDispatcher SharingStarted WhileSubscribed NETWORK RESULT SHARING TIMEOUT Result Loading ``` Should `flowThree` emit values here when collected FlowThree should emit every time flowOne or flowTwo emit values

K Merle · Answer

This works but I am not sure if it s optimal ```combine flowOne flowTwo gt flatMapLatest flowThree stateIn viewModelScope + ioDispatcher SharingStarted WhileSubscribed NETWORK RESULT SHARING TIMEOUT Result Loading ```

gildor · Answer

First should work too

gildor · Answer

difference between 1 and 2 is that in 2 you start collecting flowThree again on every flowOne and Two change

Francesc · Answer

These are not equivalent though with flatmap you are restarting the third flow at each emission of first or second

gildor · Answer

So if you have to recollect flowThree every time you have to use flatMapLatest version if it s unnecessary option 1 is better

K Merle · Answer

I do want to restart as `flowThree ` is network request

Francesc · Answer

Then use 2

gildor · Answer

simple collect is never restarting flow

Francesc · Answer

The flatmap will switch and call the method that gives you flowThree

gildor · Answer

gt I do want to restart as `flowThree ` is network request Just a question why do you need flow for this wouldn t suspend function be more clear because you would replace flatMapLatest with mapLatest map depedning on your use case and it would be clear that it require restart every time just as any other function call

K Merle · Answer

Yea you are correct I do have a Loading state already having a suspend returning a single state depending on a result seems sufficient

gildor · Answer

```viewModelScope + ioDispatcher``` And one more point Why do you need io dispatcher for this

K Merle · Answer

Isn t viewModelScope running on main thread

gildor · Answer

yes

K Merle · Answer

I didn t want to run it on main thread

gildor · Answer

Run what

K Merle · Answer

upstream of these flows

gildor · Answer

do those flows are blocking

gildor · Answer

because essentially only collction will run on iodistpatcher

gildor · Answer

with doesn t look necessary if your flows builder operations are not blocking

K Merle · Answer

I don t think they are blocking thought it would be a good practice in general to put everything to an IO by default but you might be right I might have to look around thanks

gildor · Answer

gt good practice in general to put everything to an IO by default I think it s depends what is everything you do not wrap everything to io if those operations are non blocking and the only operation which will run on IO is collection of them In our code we prefer to handle all CPU heavy IO blocking operations on level of suspend functions flow builders and do not allow them to leak further otherwise you don t really cannot believe to any suspend function to be called from main thread or even any suspend function

K Merle · Answer

I see your point Andrey never thought of that like that thanks