In compose multiplatform projects, since now screens will take up `ScreenComponent` instead of viewm...

# decompose

[Djuro]

In compose multiplatform projects, since now screens will take up ScreenComponent instead of viewmodels, what happens to the stability of compose functions. I assume there would be unnecessary recompositions since composable functions would be marked unstable since they have an unstable parameter (instance of class extending ComponentContext . How did you guys solve this?

[Arkadii Ivanov]

You can check this thread: https://github.com/arkivanov/Decompose/issues/580

[Arkadii Ivanov]

Sorry, I meant this one https://github.com/arkivanov/Decompose/discussions/581

[Djuro]

Thank you @Arkadii Ivanov

[s3rius]

By the way, the compose compiler now supports an experimental strong skipping mode that uses equals() to decide if unstable parameters should trigger recomposition.

I've been testing it for a while and it's solved most problems with unwanted recomposition with no issues (yet).

[Arkadii Ivanov]

Thanks for sharing!

[Djuro]

Very 🆒😎