How to determine which observable change caused component to re-render?

[pavelustenko]

Hello.
I'm new with mobx, but I delighted about it.
I wonder if there is some utility to track re-renders and changes in observables that caused them, alike discussed https://stackoverflow.com/questions/41004631/trace-why-a-react-component-is-re-rendering

[mweststrate]

https://mobx.js.org/analyzing-reactivity.html

…

On Thu, Oct 5, 2023 at 1:02 PM Pavel Ustenko ***@***.***> wrote: Hello. I'm new with mobx, but I delighted about it. I wonder if there is some utility to track re-renders and changes in observables that caused them, alike discussed https://stackoverflow.com/questions/41004631/trace-why-a-react-component-is-re-rendering — Reply to this email directly, view it on GitHub <#3768>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBBTQBFUYYKIA6XR5MDX52HUZAVCNFSM6AAAAAA5UCBPN2VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZVG4YDGOJUHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[domehead100]

Yes, trace, spy, intercept are incredibly useful at times. Not sure why they are being removed in Mobx v7 (per the roadmap issue).

Another manual technique that I’ve used in the past is to use Object.defineProperty to change the property descriptor, such as making it not writeable, which would cause an error when it is changed, and then you know the line of code that changed it.