ESLint Plugin: Recommend EmptyState from @wordpress/ui#77765
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: 0 B Total Size: 7.82 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 1e945c1. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/25073965575
|
|
For this to show up as an available component in the MCP added in #77159, we'll need to add |
What?
Adds
EmptyStateto the@wordpress/uiallowlist inpackages/eslint-plugin/rules/use-recommended-components.js.Why?
EmptyStateis shipped, fully tested, and ready for production use, but a direct import still triggers@wordpress/use-recommended-components. Adding the component to the allowlist matches the framing that the allowlist itself is the readiness signal. See #76135 for the broader readiness discussion.How?
Single-line addition to the
'@wordpress/ui'allowlist array, alphabetized.Testing
packages/eslint-plugin/rules/__tests__/use-recommended-components.jspasses unchanged.import { EmptyState } from '@wordpress/ui';no longer triggers@wordpress/use-recommended-components.