-
Notifications
You must be signed in to change notification settings - Fork 27.1k
Closed as not planned
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: lifecycle hooks
Milestone
Description
Which @angular/* package(s) are relevant/related to the feature request?
@angular/core
Description
@angular/core afterRender and afterNextRender are great however it is too easy to miss the distinction during a peer review and this can have a big effect on performance.
Is it possible to alias afterRender to afterEachRender or similar (I understand that it is too late to change names now).
The new name would be clear that the code attached will run multiple times (as opposed to once only if using afterNextRender).
Proposed solution
Rename afterRender to afterEachRender
Alternatives considered
Currently if used I asked the devs to import { afterRender as afterEachRender }. We could add a lint task to ensure this is done.
BTW I don't get a chance to say this elsewhere - so will say it here - thank you for all your work. Every change your team makes is so positive.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: lifecycle hooks