-
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
Prepare for adding the Widgets block editor to Core #32136
Conversation
Makes two changes required to add the Widgets block editor to Core: - Marks the @wordpress/customize-widgets package as non-private so that it can be required by Core's package.json. - Marks the Legacy Widget block as stable so that registerCoreBlocks() will register it.
c255faf
to
6c0ec79
Compare
Size Change: -42 B (0%) Total Size: 1.86 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.
LGTM 👍
enableLegacyWidgetBlock: true, | ||
} ); | ||
} | ||
__experimentalRegisterExperimentalCoreBlocks(); |
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.
@noisysocks I think this should be behind the Gutenberg phase flag like it was before.
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 guess we only needed to remove the enableLegacyWidgetBlock
option (and options object) being passed as an argument.
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.
Oh, I see #32138 now, ignore this!
Cherry-picked to the Gutenberg 10.7 release. |
Makes two changes required to add the Widgets block editor to Core (https://core.trac.wordpress.org/ticket/51506):
@wordpress/customize-widgets
package as non-private so that it can be required by Core's package.json.registerCoreBlocks()
will register it.I decided to enable Legacy Widget everywhere because:
To test: