-
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
feat: honor displayName of context types #18035
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 3968e0b:
|
Details of bundled changes.Comparing: d2158d6...3968e0b react
Size changes (stable) |
Details of bundled changes.Comparing: d2158d6...3968e0b react
Size changes (experimental) |
ea82cd5
to
1c17554
Compare
1c17554
to
0728d1f
Compare
Changed the testing approach and rebase. @bvaughn could you take a look? |
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.
This looks good. One small request.
I've had to revert this PR. Details are in #18223. |
)" (facebook#18223)" This reverts commit 3ee812e.
Thanks, Dominic! |
Summary
Any component name in errors/warnings that occur during server-side rendering ignore the
displayName
. However, react-devtools does use this property when computing the component name. The docs mention this property but are very specific about dev tools usage. Is this limitation intentional and if so: why?Test Plan
Tested by triggering a prop-types error.