Thoughts on this `Flow` extension fun (taken from ...

# codereview

[Mark]

Thoughts on this Flow extension fun (taken from here) for collecting single shot events (Android):

@Suppress("ComposableNaming")
@Composable
fun <T> Flow<T>.collectInLaunchedEffectWithLifecycle(
  vararg keys: Any?,
  lifecycle: Lifecycle = LocalLifecycleOwner.current.lifecycle,
  minActiveState: Lifecycle.State = Lifecycle.State.STARTED,
  collector: suspend CoroutineScope.(T) -> Unit
) {
  val flow = this
  val currentCollector by rememberUpdatedState(collector)

  LaunchedEffect(flow, lifecycle, minActiveState, *keys) {
    withContext(Dispatchers.Main.immediate) {
      lifecycle.repeatOnLifecycle(minActiveState) {
        flow.collect { currentCollector(it) }
      }
    }
  }
}

[Joffrey]

Mmmh, how about not using a Flow for single shot events? Flows are for streams of values and suspend functions are for single values

[Mark]

Perhaps use a viewmodel MutableState (nullable value) and get the UI to null it when done? Or do you have a specific solution in mind?

[Zach Klippenstein (he/him) [MOD]]

Why use the Dispatchers.Main.immediate dispatcher explicitly? There are cases where this will actually dispatch later than the compose dispatcher