Any changes in stack trace of updates always leads back to globalZoneAwareCallback. How do you find out what triggered the change?
I am looking any ways that can help trace the change since the time of the update. It's a pretty honest question, perhaps it's not so obvious if you are used to guessing/trial-n-error conceptually in angular 2, but as an engineer, being able to find the changes through stack trace is invaluable.
from How to debug Angular 2 with asynchronous changes?
No comments:
Post a Comment