Repository navigation
Feature: Debugging tool for mapping DOM nodes to template source #42530
Description
TL;DR: add something in the DOM during dev mode to help identify the template source file that corresponds to that DOM subtree.
I'm filing this issue on behalf of one of Google infrastructure teams. In very large applications, it can be difficult to identify a node in the DOM and then find the source location for that node. This could manifest as something like a data- attribute on component host element that references the file that contains that component's template. Other development tools could be built on top of this, such as for visualizing page composition.
Reacted by Joshua Bruning, Shawn Lauriat, Damien Engels, GBA, Jeremy Elbourn, kbae00, derek-j-pitman, Ingo Bürk, Sharon Lee, Enea Jahollari and 29 more
Activity
refactor(compiler): generate debug location instruction (angular#58982)
angular-automatic-lock-bot commentedon Jan 6, 2025
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
refactor(compiler): generate debug location instruction (angular#58982)