Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Ariakit Composite API standard #58850

Closed
3 tasks done
andrewhayward opened this issue Feb 8, 2024 · 1 comment
Closed
3 tasks done

Make Ariakit Composite API standard #58850

andrewhayward opened this issue Feb 8, 2024 · 1 comment
Assignees
Labels
[Package] Components /packages/components [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@andrewhayward
Copy link
Contributor

andrewhayward commented Feb 8, 2024

Reakit is now gone (#53278) and Composite is implemented entirely with Ariakit. However, Ariakit's API is only exported as a private V2, and the public (albeit __unstable) export is a legacy implementation designed to maintain Reakit's API.

We need to monitor usage, and decide when to...

✍️ Dev Note

@andrewhayward andrewhayward added [Package] Components /packages/components [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. labels Feb 8, 2024
@ciampo ciampo self-assigned this Jul 11, 2024
@ciampo ciampo added the Needs Dev Note Requires a developer note for a major WordPress release cycle label Jul 15, 2024
@ciampo ciampo removed the Needs Dev Note Requires a developer note for a major WordPress release cycle label Sep 5, 2024
@ciampo
Copy link
Contributor

ciampo commented Sep 5, 2024

Closing as the new implementation of Composite is now exported as a stable API, while the previous unstable version is marked as deprecated.

@ciampo ciampo closed this as completed Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Components /packages/components [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
Status: Done 🎉
Development

Successfully merging a pull request may close this issue.

2 participants