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
{{ message }}
This repository was archived by the owner on Jun 26, 2020. It is now read-only.
There is no way to know an element's key in React tab. It is omitted on the left pane and is not a prop anymore to be shown in the right pane.
As a walk-around, you can look for $key in data-reactid attribute in Chrome's own Elements tab or use $r._reactInternalInstance, but these are not the best solutions.
The text was updated successfully, but these errors were encountered:
Fixesfacebook#148.
Fixesfacebook#226.
If a `key` or `ref` is set on the React element, it's displayed before
the `props` in the tree view and in the `PropState` sidebar.
If none is set, nothing is changed.
Also removed a piece of code `Node.js` that would never run. (condition
is checked in the previous block that `return`s)
There is no way to know an element's key in React tab. It is omitted on the left pane and is not a prop anymore to be shown in the right pane.
As a walk-around, you can look for
$key
indata-reactid
attribute in Chrome's own Elements tab or use$r._reactInternalInstance
, but these are not the best solutions.The text was updated successfully, but these errors were encountered: