You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR removes the core command initialization and registration code from the edit-post and edit-site packages 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?
Remove the following from the @wordpress/edit-post and @wordpress/edit-site:
CommandMenu component and the core commands registration process
@wordpress/core-commands dependency
Moves the function that enqueues command assets to the 6.9 compat directory.
Testing Instructions
There is absolutely no change in behaviour. Confirm that all commands work correctly in the post editor, site editor, and all admin pages.
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 props-bot label.
If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
Flaky tests detected in d8ecc4b.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.
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 IS_GUTENBERG_PLUGIN check in the initializeCommandPalette, so I committed 8ad5f12.
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.
Does this mean that navigation-related commands currently in the edit-site, and editor packages will be moved to core-commands?
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
This PR removes the core command initialization and registration code from the
edit-post
andedit-site
packages 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-post
and@wordpress/edit-site
:CommandMenu
component and the core commands registration process@wordpress/core-commands
dependencyTesting Instructions
There is absolutely no change in behaviour. Confirm that all commands work correctly in the post editor, site editor, and all admin pages.