Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature: Debugging tool for mapping DOM nodes to template source #42530

Open
jelbourn opened this issue Jun 9, 2021 · 0 comments
Open

Feature: Debugging tool for mapping DOM nodes to template source #42530

jelbourn opened this issue Jun 9, 2021 · 0 comments
Labels
area: core Issues related to the framework runtime feature Issue that requests a new feature hotlist: google
Milestone
Backlog

Comments

@jelbourn
Copy link
Member

jelbourn commented Jun 9, 2021

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.
@jelbourn jelbourn added feature Issue that requests a new feature area: core Issues related to the framework runtime hotlist: google labels Jun 9, 2021
@ngbot ngbot bot modified the milestone: Backlog Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: core Issues related to the framework runtime feature Issue that requests a new feature hotlist: google
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@jelbourn