is this an bad idea? ```@Composable fun networkSt...

# compose

[Mjahangiry75]

is this an bad idea?

@Composable
fun networkState(): State<Boolean> {

    val context = LocalContext.current

    return context.networkStateFlow().collectAsState(initial = false)
}

Actually I'm trying to observe the network state in composables

[Adam Powell]

if context.nextworkStateFlow() returns a new flow instance each time (and since it looks like an extension function it probably does) you'll want to write that as

val context = LocalContext.current
return remember(context) { context.networkStateFlow() }.collectAsState(false)

[Mjahangiry75]

Thank you
could you explain why remember takes context as a parameter?

[Adam Powell]

general correctness. If LocalContext changes you want to get a new flow for the new context. In practice you probably won't actually see this ever change. But you will see this function recompose from its caller, so you do want to remember the flow.

[Mjahangiry75]

thanks a lot