-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Provide info about component tree to devtools #6549
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
b692893
Revert "Add ReactDebugInstanceMap"
gaearon e9f8d57
Add an initial implementation of ReactDebugTool events
gaearon 7884606
Handle updates to natives and composites
gaearon 804c680
Report dangerouslySetInnerHTML as no children
gaearon 1587abf
Don't report children for empty and text nodes
gaearon 367594a
Enforce that info about children is available by the time onSetChildr…
gaearon af3603e
Devtools should be able to clean up the tree on client rendering
gaearon 835ca9b
Clean up the devtool tree on server rendering
gaearon b5997c8
Extract ReactComponentTreeDevtool
gaearon f530b97
Test ReactComponentTreeDevtool specifically
gaearon ab0ef89
Track parentID for ReactPerf
gaearon 1f2e783
No need for a special case here
gaearon e20d366
Fix expect() slipping into the non-test code
gaearon 1ebffa5
ReactComponentTreeDevtool should ignore TopLevelWrapper
gaearon df3c858
Stop exposing ReactComponentTreeDevtool internal tree directly
gaearon 900a588
Add safeguards to ReactComponentTreeDevtool
gaearon 829558b
Refactor how native container ID is stored
gaearon 9f16003
Assert that unmounted instances are in the tree until purged
gaearon acd67c3
Remove isComposite and hide TopLevelWrapper
gaearon a9e0896
Mute devtool events for TopLevelWrapper and empty components
gaearon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
TANGENT:
We shouldn't do this now but as an FYI, I been thinking that the notion of a "child" component isn't limited to children. It's not in React components so why should it be in native.
AirBnB wanted to do this
<input placeholder={<CustomComponent />} />
for example which would have one of the attributes expand into a series of "children".Similar things can happen with layout I think. Anyway, let's fix that later when we know when it happens.