Skip to content

Components: Remove "Experimental" designation #59418

@mirka

Description

@mirka

Related: Tracking: stabilization of @wordpress/components props

What problem does this address?

We used to designate a component as "Experimental" as a kind of backdoor to the back-compat policy, but since the policy was made more explicit and the Private API system was introduced, the "Experimental" has become meaningless. We will need to keep supporting them as regular, shipped components.

What is your proposed solution?

  1. Add non-prefixed exports for all the __experimental prefixed exports. (We will still need to keep the prefixed versions for back-compat.)
  2. Update all documentation so they don't include __experimental in the import statements.
  3. In Storybook, move all the "Components (Experimental)" items into the main "Components" group. (Use the Storybook redirect mechanism in Storybook: Add mechanism to redirect moved stories #59181 to maintain permalinks.)

Note

This particular issue is only for the components themselves, not the __experimental props, which should be addressed separately.

PRs:

Metadata

Metadata

Assignees

Labels

[Package] Components/packages/components[Priority] HighUsed to indicate top priority items that need quick attention[Type] Code QualityIssues or PRs that relate to code quality[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions