-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Block Library: Avoid using component naming conventions for non-component code #61793
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. |
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.
👍 LGTM
Size Change: +3 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
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.
Makes sense 👍 Thanks!
…nent code (WordPress#61793) Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: ajitbohra <ajitbohra@git.wordpress.org> Co-authored-by: tyxla <tyxla@git.wordpress.org>
What?
Change names of
save
functions in the block library and avoid using React's function component naming conventions.Why?
These pure functions aren't components and shouldn't be treated as such.
Resolves errors reported by
eslint-plugin-react-compiler
. See #61788.Testing Instructions
It's a simple renaming operation. Simple smoke testing should suffice.
Testing Instructions for Keyboard
Same.