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
We will need a way to get host nodes in React DevTools with the new API. We currently get them by reaching into ReactDOMComponentTree directly but I propose to transition to using devtool API (#5306) for this so that other renderers can provide their own host nodes when they become available.
I propose that the renderer code would emit something like
It would only be called for DOM components. React DevTools would then use the ReactComponentTreeDevtool to establish the closest (DOM) component with a host node.
We will need a way to get host nodes in React DevTools with the new API. We currently get them by reaching into
ReactDOMComponentTree
directly but I propose to transition to using devtool API (#5306) for this so that other renderers can provide their own host nodes when they become available.I propose that the renderer code would emit something like
when node becomes associated and
when it is deassociated.
For DOM renderer, it would happen here.
Then we would add
getHostNode()
to ReactComponentTreeDevtool that would handleonSetHostNode
event.Does this sound reasonable? Longer term it would make something like this possible in userland.
The text was updated successfully, but these errors were encountered: