-
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
ActionItem.Slot: Render as MenuGroup
by default
#67985
base: trunk
Are you sure you want to change the base?
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: +2 B (0%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
Part of #65339
What?
Render the
ActionItem.Slot
as aMenuGroup
by default, instead ofButtonGroup
.Why?
as={ MenuGroup }
.ActionItem.Slot
s, meaning that if anyone is usingActionItem
s for anything, it is to render into the Core action item slots (which areMenuGroup
).@wordpress/interface
is an experimental package.I think this means that, although it is theoretically a breaking change, it should be safe in practice.
Testing Instructions
I couldn't get a test case set up 🙁 I've tried something like this in the Storybook, and nothing is rendering, before or after this PR:
The changes are theoretically safe and unit tests are passing, but it would be great if someone can confirm.