-
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
Color panel hook: rename to remove ambiguity #64993
Conversation
…ok was created. This commit removes the naming clash, and also any ambiguity about the color panel's hook's function.
Size Change: 0 B Total Size: 1.78 MB ℹ️ View Unchanged
|
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. |
What?
Renames
useHasBackgroundPanel
in the color panel touseHasBackgroundColorPanel
.Why?
With the introduction of the background panel an identically-named hook was created.
This commit removes the naming clash in the color panel's hook, and also any ambiguity about the color panel's hook's function.
How?
This hook is not exported outside the package, so it was find and replace job.
The hook is also used in color-panel.native.js.
Testing Instructions
CI should build and pass.
Fire up the editor and check that the color panel displays correctly as expected.