Can we invoke a function without causing recompositions? This causes everything within the current ...

# compose

[Lucas Kivi]

Can we invoke a function without causing recompositions?

This causes everything within the current @Composable scope to recompose.

val boolean by remember {
    derivedStateOf { uiState.offset.value > 0 }
}

stateHolder.handleState(boolean)

[Lucas Kivi]

this works but feels really bad because it builds a flow every time the key changes and is asynchronous…

LaunchedEffect(uiState) {
    snapshotFlow { uiState.offset.value > 0 }
        .onEach { stateHolder.handleState(boolean) }
        .collect()
}

[Lucas Kivi]

Also, if this is just a really bad idea please let me know 🙂

[Tung97 Hl]

Can you share entire the composable function?

[Lucas Kivi]

I think my issue is caused by something else..

[Tung97 Hl]

If you share the composable function entirely it will be easier to detect the issue.

[Tung97 Hl]

Because compose compiler is very magic :)))

[Lucas Kivi]

hahah ya I tried to break it down into a very simple example and the same issue didn’t occur

[Lucas Kivi]

So I think the issue I am seeing is related to something else.. I will keep investigating 🙂

[Andy Himberger]

If you remove the 'by' and use state.value only in a lambda scope where its needed you can control what composables are getting invoked when the value changes