-
Notifications
You must be signed in to change notification settings - Fork 25.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): extend the set of profiler events #59183
feat(core): extend the set of profiler events #59183
Conversation
ab7ebe4
to
6629318
Compare
This commit extends the set of events understood by the profiler integrated with the Angular time. The set got extended to account for the recently added functionality and mark entry point to the code execution points. The new set of events can be visualised by the Angular DevTools or other profiler integrations.
6629318
to
6c4b722
Compare
/** | ||
* Corresponds to the point in time just before application bootstrap. | ||
*/ | ||
BootstrapApplicationStart, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re: #59183 (comment)
Maybe it's worth it to explicitly assign values to these enum fields
TemplateCreateStart = 0,
TemplateCreateEnd = 1,
...
Not necessarily a blocker for this PR, but something to think about so that these event identifiers are more explicit instead of relying on implicit values assigned by field ordering
This PR was merged into the repository by commit 22f191f. The changes were merged into the following branches: main |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This commit extends the set of events understood by the profiler integrated with the Angular time. The set got extended to account for the recently added functionality and mark entry point to the code execution points.
The new set of events can be visualised by the Angular DevTools or other profiler integrations.