-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cases] Fix missing displayName for some react components #123460
[Cases] Fix missing displayName for some react components #123460
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
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.
Nice work!
(no fingers were exhausted typing all these changes by hand)
😆
💛 Build succeeded, but was flaky
Test FailuresMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
First part of #123375
This PR will fix most[1] of the existing components missing a displayName using the
ignoreTranspilerName
of thereact/display-name
linting rule.[1] most because there are inlined components where a longer refactor is required to set a displayName. e.g.:
in this case the react component is an anonymous function and enabling
ignoreTranspilerName
will make this file fail but it is harder to auto-fix.All these files were "auto-fixed" using a custom fixing script. https://gist.github.com/academo/f2bc72d733e6fe1d5960b3b9b37247ae (no fingers were exhausted typing all these changes by hand)