-
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
Block Editor: Move 'ParentSelectorMenuItem' into a separate file #59146
Conversation
Size Change: +4 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
Flaky tests detected in bfa2827. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7947571090
|
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 🚀
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. |
Thanks for the review, @t-hamano! |
What?
PR moves the
BlockParentSelectorMenuItem
component into its separate file.Why?
This matches the standard we're using for most of the menu items.
P.S. The
CopyMenuItem
is small enough that I think it's okay to keep collating it.Testing Instructions
Testing Instructions for Keyboard
Same.
Screenshots or screencast