```dataStoreManager.getShopDomain().distinctUntilChanged().collectLatest { shop -> da...

# coroutines

[Mohammed Akram Hussain]

dataStoreManager.getShopDomain().distinctUntilChanged().collectLatest { shop ->
            dataStoreManager.getStorefrontAccessToken().distinctUntilChanged().collectLatest { accessToken ->
                    if (shop.isNotEmpty() && accessToken.isNotEmpty()) {
                        // Build the graph client

I need to collect from two flows and do something but having nested collectLatest is making me think if it's the right approach? Is there a better way which does the same as above?

[stojan]

combine on the two flows

[Mohammed Akram Hussain]

combine is behaving differently than collectLatest

[ephemient]

combine(f, g) { x, y -> x to y }.collectLatest { (x, y) ->

[gildor]

Maybe I'm missing something, but isn't it what combineLatest(f, g) does?

[Mohammed Akram Hussain]

I think combineLatest has been deprecated for combine

[gildor]

Ah, I got what is the issue, combineLatest is our own utility, haha, sorry for confusion.
Implemented like this, if you curious (+ other overloads for 3-4 flows):

fun <T1, T2, R> combineLatest(
    flow: Flow<T1>,
    flow2: Flow<T2>,
    transform: suspend (T1, T2) -> R
): Flow<R> = combine(flow, flow2) { t1, t2 -> listOf(t1, t2) }
    .mapLatest { args ->
        @Suppress("UNCHECKED_CAST")
        transform(
            args[0] as T1,
            args[1] as T2
        )
    }

[Mohammed Akram Hussain]

Great, thank you very much for that! It behaves exactly as what I wanted.