-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Command Palette: Enqueue assets globally #71264
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
Conversation
| add_settings_field( | ||
| 'gutenberg-command-palette-everywhere', | ||
| __( 'Command Palette: enable everywhere', 'gutenberg' ), | ||
| 'gutenberg_display_experiment_field', | ||
| 'gutenberg-experiments', | ||
| 'gutenberg_experiments_section', | ||
| array( | ||
| 'label' => __( 'Enables the Command Palette everywhere in the admin dashboard.', 'gutenberg' ), | ||
| 'id' => 'gutenberg-command-palette-everywhere', | ||
| ) | ||
| ); |
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.
This setting does nothing anymore, but I forgot to remove it 😅
|
Size Change: -53 B (0%) Total Size: 1.92 MB
ℹ️ View Unchanged
|
|
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. |
|
Flaky tests detected in d8ecc4b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/17143369042
|
youknowriad
left a comment
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.
This is working great for me. I don't see any issues.
One thing I noticed is that I would love if we do some kind of audit/unification of all the navigation commands. Maybe all of them should be "go to something" and work in all screens. Right now it's a bit inconsistent. I think we use "open something" a bit more but sometimes we do nothing like just "styles"...
|
I forgot to delete the
Does this mean that navigation-related commands currently in the |
That sounds like a good approach to me, also unifying labels... |
I see, I'd like to submit an issue to address that later 👍 |
|
I'd like to add this PR to the 6.9 Editor Tasks board so that we don't forget to commit the core patch in 6.9 Beta 1 release. |
Since the core ticket has the |
What?
This PR removes the core command initialization and registration code from the
edit-postandedit-sitepackages and enqueues command-related assets globally.Why?
We need to eliminate the Post Editor and Site Editor-specific processing and register commands with one code.
How?
@wordpress/edit-postand@wordpress/edit-site:CommandMenucomponent and the core commands registration process@wordpress/core-commandsdependencyTesting Instructions
There is absolutely no change in behaviour. Confirm that all commands work correctly in the post editor, site editor, and all admin pages.