Experiment: Fix console errors/warnings for taxonomies#77601
Conversation
| import type { Field, Form } from '@wordpress/dataviews'; | ||
| import { Stack } from '@wordpress/ui'; | ||
| // eslint-disable-next-line @wordpress/use-recommended-components -- Used here because it supports rendering as a `span` via the `render` prop to avoid invalid HTML. | ||
| import { Notice, Stack } from '@wordpress/ui'; |
There was a problem hiding this comment.
I'm using the Notice component from UI component which while not recommended yet officially, it's fine for the experiment and will keep an eye on it for when is stabilized.
|
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.76 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 7aa2c61. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24828444402
|
tyxla
left a comment
There was a problem hiding this comment.
This looks good and tests well, and the console errors are fixed 👍
Thanks!
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org> Co-authored-by: tyxla <tyxla@git.wordpress.org> Co-authored-by: simison <87168+simison@users.noreply.github.com>

What?
This PR fixes some console errors/warnings for taxonomies.
Testing instructions
edita taxonomy and change thetaxonomy-keywhich will render the notice. Observe no related console errors/warnings in dev tools