Replies: 3 comments
-
Also With coroutines debug probles, we have to call |
Beta Was this translation helpful? Give feedback.
0 replies
-
This question is better asked of the Google team working on the compose runtime. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sure. I have asked Google here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As an application becomes more complex, the difficulty of determing what is causing a recomposition increases. No amount of skill or experience can allow you to quickly identify what triggered the recomposition, it is just a major chore.
In the best case, it would be super useful if we could do something like this:
recompositionCause
here is a debugging statement, not to be used in production code. Its performance does not matter at all.I expect it to print something like:
Is this at all possible?
From googling, I see that Android Studio has some tools built into the IDE that help with identifying recomposition triggers. However, I'm looking for something that works on multplatform (desktop, in particular) and that doesn't require the IDE at all.
Beta Was this translation helpful? Give feedback.
All reactions