Repository navigation
Conversation
🤖 PR meta 🤖🎉 PropsIf 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. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: +128 B (0%) Total Size: 8.68 MB 📦 View Changed
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
🏁 Flaky testsSome 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. does not select blocks in the canvas preview when editing from the sidebar in
|
| since: '7.3', | ||
| version: '7.6', |
| import UI from '@wordpress/ui'; | ||
| import { Tabs } from '@wordpress/ui'; | ||
| import { Radio, RadioGroup, RadioGroupControl } from '@wordpress/ui'; | ||
| import { SelectControl } from '@wordpress/ui'; |
There was a problem hiding this comment.
This doesn't seem to add any new information as another example here.
There was a problem hiding this comment.
This made me notice we actually don't publicly export some validated components, including the one for CustomSelectControl. Let me remove those from the package first (#87089), and then we won't need to have a separate deprecated.tsx.
There was a problem hiding this comment.
Sounds good, I'll wait
See #80412.
What?
Soft-deprecate
CustomSelectControlfrom@wordpress/componentsin WordPress 7.3. UseSelectControlfrom@wordpress/uifor new code, or composeSelectfor the small size.Why?
Gutenberg's direct consumers have migrated. The public warning gives plugin and theme authors a migration guide while their existing controls continue to work.
How?
Wrap the public export with a deprecation warning.
ValidatedCustomSelectControlcontinues to render the internal control without a warning. Move the legacy stories under Deprecated, keep their existing IDs, and update the ESLint guidance.Proposed removal version
Veloria found 152 identifier matches across 32 plugins and two matches in one theme. These are search hits, and some are changelog entries or comments. I confirmed direct imports in Super Web Share and Blocksy. The draft proposes WordPress 7.6 to give consumers three release cycles to migrate. Recheck usage before removal.
Plugin search · Theme search
Testing Instructions
?path=/story/components-customselectcontrol--default. Open the console and reload the story. Confirm it logs one deprecation warning with the migration guide link.Use of AI Tools
Codex implemented and tested the changes and drafted this description.