Shadows: Unlock private components and hooks at the file level#61790
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: +46 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
tyxla
left a comment
There was a problem hiding this comment.
Tests well and code looks good 👍
|
Did you check this for the whole package? |
|
@ellatrix, I fixed the ones reported by the new linter plugins. It was a manual effort updating similar code, but at least now we have a linter for it. There are a couple more, but they are unrelated to the private APIs. |
…ress#61790) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: tyxla <tyxla@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
What?
A micro-optimization moves the private
Compositecomponent and hook unlocking outside the components, at the file level.Why?
Resolving an error reported by
eslint-plugin-react-compiler. See #61788.This is similar to #55809.
Testing Instructions
Testing Instructions for Keyboard
Same.
Screenshots or screencast