Restrict base-ui imports outside of UI component packages#75143
Restrict base-ui imports outside of UI component packages#75143
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: -8 B (0%) Total Size: 3 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 39e0610. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/21599739044
|
Co-authored-by: Andrew Duthie <[email protected]>
Co-authored-by: Andrew Duthie <[email protected]>
366ec41 to
242267d
Compare
* Restrict base-ui imports outside of UI component packages * Update .eslintrc.js Co-authored-by: Andrew Duthie <[email protected]> * Update .eslintrc.js Co-authored-by: Andrew Duthie <[email protected]> * Add comments back, format --------- Co-authored-by: ciampo <[email protected]> Co-authored-by: aduth <[email protected]>
What?
Restrict importing from
@base-ui/reactin the codebase, except for the@wordpress/uipackage.Why?
Those libraries are meant to be abstracted by, and consumed via the
@wordpress/uipackage.How?
Update ESLint settings.
Testing Instructions
@wordpress/uipackage should not cause lint errors@wordpress/uipackage should cause a lint error