-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Editor: Serve as a proxy for the interface package #60748
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: -5.1 kB (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
5dcc585
to
3bba509
Compare
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 smoke tested the editors and didn't notice anything different.
Related #52632
What?
As you align editor APIs between post and site editors, we'll have to align extensibility APIs that rely on the interface package.
This package is a bundled package (bundled within the package that import it) and it also defines a store, which means it can't be imported both from "editor" and "edit-post" at the same time. (Triggers an error about double store).
I think having a "store" in this package was an error that we made a long time ago, so it's hard to change now in one go, so in order to avoid this issue, we can make the editor package work as a proxy for the "interface" package APIs for both edit-post and edit-site.
So the current PR does exactly that to allow us to make further unification as follow-ups.
Testing Instructions
There should be no functional change, it's mostly about moving things around.