![]() In that case, it is up to the framework to use the API, you don’t need to worry about it. Most of the time, the framework you are using handles the scheduling and async execution. See Modern debugging in DevTools to learn more.ĭoes it sound complicated? Not at all. You can tell the whole story of the operation by linking both parts of the async code together with the new console.createTask() method. With the latest changes, DevTools now shows the operation originates from the onClick event in the button component, then the increment function, followed by the timeout operation.īehind the scenes, DevTools introduced a new “Async Stack Tagging” feature. It did not show the “root cause” of the operation. Previously, the stack trace only showed the timeout operation. In our source code, the operation includes an async timeout operation. Previously, it tells only part of the story.įor example, open this demo and click on the increment button. When some operations are scheduled to happen asynchronously, the stack traces in DevTools now tell the “full story” of the operation. Enable the Group files by Authored / Deployed setting to view your original source code (Authored) first and navigate to them quicker.Ĭhromium bug: 1352488 # Improved stack traces # Linked stack traces for asynchronous operations Previously, it showed directly on the navigation pane. ![]() ![]() The Group files by Authored / Deployed is now shown under the 3-dot menu. # Group files by Authored / Deployed in the Sources panel
0 Comments
Leave a Reply. |