-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Gutenberg: Audit experimental feature usage. #44251
Comments
Do we need to watch |
Related upstream tracking issue: WordPress/gutenberg#25786 |
Make sure they don't break when the experimental feature goes away (undefined errors, etc), ping the right people about that, see if issues need to be created. Perhaps the best way would be to start with a P2 post. |
Found just one occurrence here. Added to the Editing Toolkit tracking issue. |
@WunderBart Can you compare our feature usage with WordPress/gutenberg#25786? That should help give us an idea of what things are priorities. |
At this point we know that the following will not be considered as stable in 5.6: Block Editor
Selectors
Components
PropsBlock Preview
Block Navigation
Block API
|
Closing this as of #47712 / p4TIVU-9xW-p2 |
There are many experimental features in use right now. Audit them. See docs about these APIs.
This is a master tracking issue for the following:
Milestone: https://github.com/Automattic/wp-calypso/milestone/324
Gutenberg Experimental API Audit: WordPress/gutenberg#25786
The text was updated successfully, but these errors were encountered: