-
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
[DevTools Bug]: DevTools shouldn't skip over keyed Fragments in the tree #25187
Comments
gaearon
added
Type: Bug
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
Component: Developer Tools
labels
Sep 5, 2022
Hi @gaearon, I would like to give it a shot, if you think this bug is a beginner friendly. Could you please point which exact package should I look at? I see there are seven of them related to devtools:
|
lunaruan
removed
the
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
label
Sep 6, 2022
lunaruan
added a commit
that referenced
this issue
Sep 7, 2022
resolves #25187 --- We shouldn't hide fragments that have a key because this is important information that the user might want in the future.
sammy-SC
pushed a commit
that referenced
this issue
Sep 11, 2022
resolves #25187 --- We shouldn't hide fragments that have a key because this is important information that the user might want in the future.
rickhanlonii
pushed a commit
that referenced
this issue
Oct 5, 2022
resolves #25187 --- We shouldn't hide fragments that have a key because this is important information that the user might want in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Website or app
reactjs/react.dev#4981
Repro steps
<Fragment key="stuff">
We filter out fragments because they tend to be useless. But this one is important! Keys are crucial and we should show anything with a key in the tree.
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
The text was updated successfully, but these errors were encountered: