Really smart about it and does its best to do this optimization out of the box when it has enough information available (for example, all parameters that are primitives are stableīy design).
If you are new to this topic, I go in a lot more detail about Recomposition in this article.įor most use-cases, we don't want a composable function to be reinvoked unless its parameters changed (this is an oversimplification). By skipping all functions or lambdas that don't have changed parameters, Compose can recompose efficiently. When Compose recomposes based on new inputs, it only calls the functions or lambdas that might have changed, and skips the rest. This happens when the function's inputs change. Recomposition is the process of calling your composable functions again when inputs change. It's called Recomposition and it is fundamental to how Compose operates. One concept that's been the source of a lot of confusion. In spite of all the documentation, there's There's a significant amount of documentation already available for helping developers embrace this new paradigm.
0 kommentar(er)
