-
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: Remove expired __experimentalGroup deprecations and prop #56023
base: trunk
Are you sure you want to change the base?
Conversation
With the release of 6.4, the deprecated old __experimentalGroup prop can now be removed.
Size Change: -96 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
Flaky tests detected in 395b9f1. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6818623580
|
I wanted to make sure everyone reviewing is aware that it’s going to impact production websites that still use the experimental prop for the group name. In effect, the controls impacted will move to the default group in the sidebar. The fact that the core block had to get refactored as part of the task triggered my feedback. There is no issue with that from the code perspective, but it might disturb the user experience, so it would be good to run a brief check in the plugin directory to see if there is anything to worry about. |
Thanks @gziolo, I'll dig deeper into the plugin directory next week to see what we're looking at 👍 |
I like that even if there's a plugin that is already using this won't break with this PR. It will just move to a different part of the toolbar. That said, a look into the plugin directory and some reaching out might be good. |
Unfortunately, it looks like there still could be some breakage. Most of the InspectorControl groups render into a ToolsPanel. Any ToolsPanelItems rendered into the non-advanced/default groups by plugins would be broken. There are a some hits when searching for current uses of The majority of these hits were for It would be good to properly clean up the experimental props but I'm not certain on how best we achieve that. Is there a formal process for reaching out to plugin authors to resolve some of these outstanding uses of cc/ @annezazu |
So sorry for the delay here. Came back from nearly two weeks off and am just now catching up here. I usually just reach out manually and ask folks to look at this PR/share their feedback/get prepared. Sometimes that means doing some internet digging to actually find people. If you'd like, I can handle that this week :) |
That would be amazing, thank you Anne! 🙇 |
Reached out to every impacted plugin that has active installs. If there are 0 installs, I didn't reach out (but I can if we want). The only person I couldn't track down is the creator of Custom Content Blocks. The GitHub profile seems to be @alexlundin so noting that here. |
Related:
What?
Completes the removal of the deprecated
__experimentalGroup
prop from inspector controls fills and slots.Why?
__experimentalGroup
was stabilised into thegroup
prop. With the release of WP 6.4, the deprecation of__experimentalGroup
has expired and can now be removed.How?
__experimentalGroup
prop anddeprecated()
calls.Testing Instructions
__experimentalGroup
in code