-
Notifications
You must be signed in to change notification settings - Fork 46.4k
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.
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
Walk down internal tree to find DOM node #4988
Conversation
@sebmarkbage This one's for you too. Does adding |
769d0ee
to
a39217a
Compare
^^ Updated to simplify code and remove empty component registry (now unnecessary!). |
Looks good to me, I'm assuming this is also destined for 0.15. |
Yes. |
472739d
to
d7d9de1
Compare
@sebmarkbage You said you'd prefer to store the rendered node type (native, composite, or empty) on each composite rather than the actual element/node. Like this? |
EMPTY: 2, | ||
|
||
getType: function(node) { | ||
if (node === null || node === false) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this logic should be shared for guaranteed consistency? (instantiateReactComponent has it too)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah maybe that should use this.
This reduces our reliance on hierarchical IDs.
Walk down internal tree to find DOM node
@spicyj updated the pull request. |
This reduces our reliance on hierarchical IDs.