You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A resource used as styleUrl by one component and templateUrl by another never dispatches the template owner #450
Split out of a Codex review finding on #449. Pre-existing on main — not introduced by that PR.
Symptom
One file serves two decorator roles: component A lists it in styleUrls, component B uses it as templateUrl. Editing the file dispatches angular:component-update for A only. B keeps rendering the old template.
Cause
handleHotUpdate treats the two roles as mutually exclusive branches. isDirectStyle (directStyleUrls.has) selects the style path, and the template-owner loop sits in the else:
The same fork exists on main before #449: the else held resourceToComponent.get, equally unreachable for a dual-role file. #449 documents this corner but does not change it.
Suggested fix
Run the two owner loops independently instead of forking on isDirectStyle: process style owners when the file is a direct style, AND template owners when it is a direct template. handled semantics and the template self-accept mark need review when both roles fire for one edit.
Activity
fix(vite): dispatch HMR for both decorator roles of one resource (voi…