Skip to content

refactor(devtools): combine element name and nativeElement into element object#69135

Draft
eduhmc wants to merge 1 commit into
angular:mainfrom
eduhmc:refactor-devtools-node
Draft

refactor(devtools): combine element name and nativeElement into element object#69135
eduhmc wants to merge 1 commit into
angular:mainfrom
eduhmc:refactor-devtools-node

Conversation

@eduhmc
Copy link
Copy Markdown

@eduhmc eduhmc commented Jun 3, 2026

This refactoring combines the 'element' (tagName string) and 'nativeElement' (DOM Node) properties of DevToolsNode into a single 'element' object. This cleans up the interface and makes it clearer what is serializable.

@eduhmc eduhmc requested a review from csmick June 3, 2026 20:57
@pullapprove pullapprove Bot requested a review from hawkgs June 3, 2026 20:57
@ngbot ngbot Bot added this to the Backlog milestone Jun 3, 2026
@eduhmc eduhmc marked this pull request as draft June 3, 2026 20:58
@eduhmc eduhmc removed the request for review from hawkgs June 3, 2026 20:58
nativeElement: undefined,
element: {
tagName: ELEMENT_NAME_MAP[controlFlowBlock.type],
node: undefined,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't realize there was a case where a tag name could be present without an associated node. In that case, it might make more sense to leave these properties as-is.

…nt object

This refactoring combines the 'element' (tagName string) and 'nativeElement' (DOM Node) properties of DevToolsNode into a single 'element' object. This cleans up the interface and makes it clearer what is serializable.
@eduhmc eduhmc force-pushed the refactor-devtools-node branch from 2fabe24 to 3c5267a Compare June 3, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants