Giving it a try now... but I'm getting an error in Android Studio that flow operators shouldn't be u...

# squarelibraries

[dave08]

Giving it a try now... but I'm getting an error in Android Studio that flow operators shouldn't be used in composables... will I have to do @SuppressLint("FlowOperatorInvokedInComposition") for each of them? It seems to me that in the context of Molecule presenters there's no real problem in transforming/filtering flows... maybe there's a way for the library to suppress those warnings for it's functions somehow?

[hfhbd]

You should use collectAsState instead.

[dave08]

val installState by applicationStatus
    .filter { it.packageName == summary.packageName }
    .flatMapLatest { it.progressFlow }
    .collectAsState(initial = InstallState.None)

Gives me that error

[dave08]

The filter and flatMapLatest bothers AS...

[jw]

It needs remembered

[dave08]

Then I get Composable calls are not allowed inside the calculation parameter of inline fun <T> remember(crossinline calculation: () -> TypeVariable(T)): TypeVariable(T) on collectAsState

[jw]

collectAsState goes on the outside

[jw]

You want to remember the computation of the Flow

[jw]

And then collect that final flow in the composition

[hfhbd]

val installState by remember { applicationStatus
    .filter { it.packageName == summary.packageName }
    .flatMapLatest { it.progressFlow } }
    .collectAsState(initial = InstallState.None)

[dave08]

👍🏼

[dave08]

Thanks! And now I don't need to suppress any IDE warnings... AND I learned that even Molecule needs remember... it feels funny since in a ViewModel you don't usually need it, and in the docs, there's no mention of it.

[hfhbd]

Yeah, but this is unrelated to molecule, just the basic behaviour of compose and recomposition on state changes

[jw]

It's not Molecule, it's performing unnecessary computation on each composition. Any flow would need it.