-
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
editPost: deprecate __experimentalPluginPostExcerpt #61188
editPost: deprecate __experimentalPluginPostExcerpt #61188
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: +108 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
@@ -161,6 +160,6 @@ export function reinitializeEditor() { | |||
|
|||
export { default as __experimentalFullscreenModeClose } from './components/header/fullscreen-mode-close'; | |||
export { default as __experimentalMainDashboardButton } from './components/header/main-dashboard-button'; | |||
export { __experimentalPluginPostExcerpt }; |
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 might be already used by third-party devs, so we should at least deprecate it and not remove it.
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.
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.
not all code is in public repos/plugins :)
It seems that after a third-party search above, the component is not used at all and since it's an experimental one, we might consider just deprecating it (without actually making it stable). Especially given that the UI for the excerpt panel is changing cc @ntsekouras |
We'd like to extend it in the Jetpack plugin. |
@retrofox did you consider replacing the existing panel instead? It seems like a potentially better approach?
|
|
Yes, indeed that was the original and current implementation. |
a603e9a
to
d1d4a7f
Compare
The problem with extending it is that it's not a really well defined API. What does extending it really means? Also removing is something we consistently support for panels so it's a good idea to keep the consistency between panels and not have an API for one panel adhoc. |
I've updated PR and its description. In short:
The question is should or shouldn't expose it |
Flaky tests detected in 82889e5. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8878173940
|
This breaks backward compatibility for an API exposed in a stable version of WordPress. I've opened #61219 as a follow up for replacing the noop function with a proper deprecation process that maintains backward compatibility. |
Thank you, Peter. We have created a follow-up and would appreciate it if you could take a look at it |
What?
It deprecates
__experimentalPluginPostExcerpt
component in theeditPost
package,and exposes thePluginPostExcerpt
component in theeditor
package.Follow up of #57096
Addressing this feedback.
Why?
Because we stopped using these prefixes.
How?
wp.editPost.__experimentalPluginPostExcerpt
from 6.6.Introducewp.editor.PluginPostExcerpt
from 6.6Testing Instructions
Check component functions
wp.editPost.__experimentalPluginPostExcerpt
is definedwp.editPost.__experimentalPluginPostExcerpt
is deprecatedTesting Instructions for Keyboard
Screenshots or screencast