-
Notifications
You must be signed in to change notification settings - Fork 4.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
Block Bindings: Remove client core sources registration in widgets #67349
Block Bindings: Remove client core sources registration in widgets #67349
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: -59 B (0%) Total Size: 1.82 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.
Thanks so much for addressing this!
This LGTM:
✅ The PHP notice is gone in classic themes
✅ I smoke tested the widget editor, all works as expected
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.
Also tests well for me.
…ordPress#67349) * Remove client core sources registration in widgets * Remove dependencies Co-authored-by: SantosGuillamot <[email protected]> Co-authored-by: ramonjd <[email protected]> Co-authored-by: talldan <[email protected]> Co-authored-by: gziolo <[email protected]> Co-authored-by: youknowriad <[email protected]>
…67349) * Remove client core sources registration in widgets * Remove dependencies Co-authored-by: SantosGuillamot <[email protected]> Co-authored-by: ramonjd <[email protected]> Co-authored-by: talldan <[email protected]> Co-authored-by: gziolo <[email protected]> Co-authored-by: youknowriad <[email protected]>
What?
Potential fix for #67333.
It removes the client-side registration of core sources in widgets screens. As discussed in the original issue, I think it is okay to keep support only in the server for these use cases.
Why?
It seems the
@wordpress/editor
package shouldn't be imported inedit-widgets
andcustomize-widgets
packages.How?
I just removed the function to register core sources in the editor from the widgets screen.
Testing Instructions
Go through the testing instructions in the original issue and check it is solved.