UI Icon: Mark as recommended#78365
Conversation
|
Size Change: 0 B Total Size: 7.97 MB ℹ️ View Unchanged
|
| componentStatus: { | ||
| status: 'recommended', | ||
| status: 'use-with-caution', | ||
| whereUsed: 'global', | ||
| notes: 'Prefer this component over the `Icon` component from `@wordpress/icons`.', | ||
| notes: 'When rendering SVGs, use `Icon` from `@wordpress/ui` instead.', | ||
| }, |
There was a problem hiding this comment.
I'm not in a hurry to ban this in the use-recommended-components lint, because there are some usage patterns that are intentionally not supported in the new Icon component.
It would probably be better to audit those unsupported usage patterns and have some migration guidance ready first.
There was a problem hiding this comment.
we all love a good dashicon
|
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. |
|
Flaky tests detected in a0a8460. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/25935224784
|

What?
Part of #76135
Marks
Iconfrom@wordpress/uias recommended for use, and updates the legacyIconcomponent guidance in@wordpress/components.Import renaming for the legacy component is done in #78366.
Why?
The UI package
Iconis the preferred renderer for SVG icons as the design system components move toward broader adoption.Testing Instructions
See Storybook docs for both
Iconcomponents.