-
Notifications
You must be signed in to change notification settings - Fork 48.8k
Move createElement/JSX Warnings into the Renderer #29088
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
Changes from all commits
bde00cc
8086702
c359809
90971dc
8f6c117
caa9078
06a041a
047439c
43ceacd
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
|
@@ -1932,9 +1932,8 @@ describe('Store', () => { | |||||||
); | ||||||||
|
||||||||
expect(store).toMatchInlineSnapshot(` | ||||||||
✕ 1, ⚠ 0 | ||||||||
[root] | ||||||||
▾ <Example> ✕ | ||||||||
▾ <Example> | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any chance we can get these back? It was part of the feature that you could jump to the element in devtools to find the offending element quickly. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yea. So this is directly related to this TODO: react/packages/react-reconciler/src/ReactChildFiber.js Lines 178 to 180 in fe72cfc
Previously it was the "owner" of the parent which sometimes isn't related to where these elements are created at all. Now it's the actual child that should have the key specified on it but since that's a fake fiber it is not persistent in DevTools. We need to refactor ChildFiber to allow this warning to happen when we have access to the real fiber and it'll be better for context but I'm not planning on doing that yet because the rest of it is too much work already. |
||||||||
<Child> | ||||||||
`); | ||||||||
}); | ||||||||
|
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.
I got confused by this for a bit. I thought it suggested I should look inside
ParentClient
.What do you think about
?
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.
I want to remove this whole contextual thing once we ship the owner stacks. It makes no sense and is kind of an artifact of trying to explain the actual cause which we don't have. I just didn't want to change it yet to keep parity in the incremental steps. Mainly because of all the tests. The current PR I'm working on I'm manually editing hundreds of tests. I'm actually doing a lot of incremental stuff I wouldn't do just because editing our tests is too much work.