From f206d1041fee6943daf3d544dc3add0e95fb34d7 Mon Sep 17 00:00:00 2001 From: Gerald Monaco Date: Mon, 16 Oct 2023 19:59:44 +0000 Subject: [PATCH] refactor(core): use performance API for afterRender feature logging (#52235) Add a standard performance marker that can be viewed in Chrome Dev Tools and other tooling. See more info at https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark PR Close #52235 --- packages/core/src/render3/after_render_hooks.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/packages/core/src/render3/after_render_hooks.ts b/packages/core/src/render3/after_render_hooks.ts index f0c837a0422..f55e8b5557d 100644 --- a/packages/core/src/render3/after_render_hooks.ts +++ b/packages/core/src/render3/after_render_hooks.ts @@ -224,6 +224,8 @@ export function afterRender(callback: VoidFunction, options?: AfterRenderOptions return NOOP_AFTER_RENDER_REF; } + performance.mark('mark_use_counter', {detail: {feature: 'NgAfterRender'}}); + const afterRenderEventManager = injector.get(AfterRenderEventManager); // Lazily initialize the handler implementation, if necessary. This is so that it can be // tree-shaken if `afterRender` and `afterNextRender` aren't used. @@ -298,6 +300,8 @@ export function afterNextRender( return NOOP_AFTER_RENDER_REF; } + performance.mark('mark_use_counter', {detail: {feature: 'NgAfterNextRender'}}); + const afterRenderEventManager = injector.get(AfterRenderEventManager); // Lazily initialize the handler implementation, if necessary. This is so that it can be // tree-shaken if `afterRender` and `afterNextRender` aren't used.