-
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
Migrate customize widgets editor to use new preferences package #39112
Migrate customize widgets editor to use new preferences package #39112
Conversation
Size Change: -405 B (0%) Total Size: 1.15 MB
ℹ️ View Unchanged
|
|
||
.components-popover.customize-widgets-more-menu__content { | ||
z-index: z-index(".components-popover.customize-widgets-more-menu__content"); | ||
} |
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.
I don't understand 😅 Why is all of this CSS no longer needed?
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.
Aha, the description of #39113 answered my question!
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.
It hasn't really been needed for a while. It's identical to the css implemented by the base component in the interface package:
https://github.com/WordPress/gutenberg/blob/trunk/packages/interface/src/components/more-menu-dropdown/style.scss
I realised I could've deleted it for edit-widgets too, so I've made a small PR here to do that - #39113
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 for cleaning it up!
() => | ||
!! wp.data | ||
.dispatch( 'core/preferences' ) | ||
.toggleFeature( |
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.
Should this be toggle
?
() => | ||
!! wp.data | ||
.select( 'core/preferences' ) | ||
.isFeatureActive( 'core/customize-widgets', 'welcomeGuide' ) |
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.
Should this be get
?
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.
yes 😮
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.
Nice PR you have here 👍
Description
Addresses some of #31965, follows #39084
Migrates the customize widgets editor to use the new preferences package (introduced in #38873). Previously it was using interface, but the plan is now to deprecate the preferences APIs in interface in favor of this new package.
The main goal here is that nothing is different from a user perspective.
Testing Instructions
trunk
open the customize widgets editor and dismiss the welcome guideChecklist:
*.native.js
files for terms that need renaming or removal).