Components: update React function names for better ESLint detection#77148
Components: update React function names for better ESLint detection#77148
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: -164 B (0%) Total Size: 7.74 MB 📦 View Changed
ℹ️ View Unchanged
|
|
Flaky tests detected in 5c5e1a4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24178774005
|
|
Trying to remember why I prefixed that component with |
|
I guess this is ready to be shipped? |
|
Yeah, it should be good to merge. Not sure if similar minor internal changes warrant a changelog entry. |
97a78de to
5c5e1a4
Compare
|
Thanks @ciampo for confirmation, I now added also a changelog entry and triggered auto-merge. |
Spinoff from ESLint upgrade in #76654. Updates React component names so that ESLint recognizes them as React components and allows hooks usage inside. The
_prefix prevented that detection.I'm removing prefixes from
CustomSelectthat seem unnecessary. @ciampo can you confirm that this is OK? The only identifier that keeps the prefix is_CustomSelectPropsbecause there is alsoCustomSelectProps. The difference is some magic with the type of thesizecomponent, I don't understand this.There's also a
Sandboxname update, using theUnforwardedSandboxconvention to prevent a "no shadow" lint error.After this, #76654 can remove a few disable comments.