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

Gutenberg: Audit experimental feature usage. #44251

Closed
3 tasks
sirreal opened this issue Jul 17, 2020 · 7 comments
Closed
3 tasks

Gutenberg: Audit experimental feature usage. #44251

sirreal opened this issue Jul 17, 2020 · 7 comments
Assignees
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg [Type] Task

Comments

@sirreal
Copy link
Member

sirreal commented Jul 17, 2020

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

@sirreal
Copy link
Member Author

sirreal commented Sep 22, 2020

Do we need to watch __unstable as well?

@ockham
Copy link
Contributor

ockham commented Oct 5, 2020

Related upstream tracking issue: WordPress/gutenberg#25786

@fullofcaffeine
Copy link
Contributor

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.

@WunderBart WunderBart self-assigned this Oct 14, 2020
@WunderBart
Copy link
Member

Do we need to watch __unstable as well?

Found just one occurrence here. Added to the Editing Toolkit tracking issue.

@sirreal
Copy link
Member Author

sirreal commented Oct 16, 2020

@WunderBart Can you compare our feature usage with WordPress/gutenberg#25786? That should help give us an idea of what things are priorities.

@WunderBart
Copy link
Member

WunderBart commented Oct 16, 2020

@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

  • __experimentalLinkControl (unused)

Selectors

  • __experimentalGetAllowedBlocks (unused)

Components

Props

Block Preview

  • __experimentalPadding (unused)

Block Navigation

Block API

  • __experimentalGetAccessibleBlockLabel (unused)
  • __experimentalGetBlockLabel (unused)

@sirreal
Copy link
Member Author

sirreal commented Nov 27, 2020

Closing this as of #47712 / p4TIVU-9xW-p2

@sirreal sirreal closed this as completed Nov 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg [Type] Task
Projects
None yet
Development

No branches or pull requests

4 participants