Wp-calypso: Gutenberg: Audit experimental feature usage.

Created on 17 Jul 2020  路  6Comments  路  Source: Automattic/wp-calypso

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: https://github.com/WordPress/gutenberg/issues/25786

[Goal] Gutenberg [Type] Task

Most helpful comment

@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

  • __experimentalBoxControl (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalInputControl (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalNumberControl (unused)
  • __experimentalUnitControl (unused)

Props

Block Preview

  • __experimentalPadding (unused)

Block Navigation

  • __experimentalBlockNavigationBlockFill (unused)
  • __experimentalBlockNavigationEditor (unused, proposed to be removed in https://github.com/WordPress/gutenberg/pull/25069)
  • __experimentalBlockNavigationTree (unused)
  • __experimentalTreeGrid (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalTreeGridCell (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalTreeGridItem (unused)
  • __experimentalTreeGridRow (used, see https://github.com/Automattic/wp-calypso/issues/46496)

Block API

  • __experimentalGetAccessibleBlockLabel (unused)
  • __experimentalGetBlockLabel (unused)

All 6 comments

Do we need to watch __unstable as well?

Related upstream tracking issue: https://github.com/WordPress/gutenberg/issues/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.

Do we need to watch __unstable as well?

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

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

@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

  • __experimentalBoxControl (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalInputControl (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalNumberControl (unused)
  • __experimentalUnitControl (unused)

Props

Block Preview

  • __experimentalPadding (unused)

Block Navigation

  • __experimentalBlockNavigationBlockFill (unused)
  • __experimentalBlockNavigationEditor (unused, proposed to be removed in https://github.com/WordPress/gutenberg/pull/25069)
  • __experimentalBlockNavigationTree (unused)
  • __experimentalTreeGrid (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalTreeGridCell (used, see https://github.com/Automattic/wp-calypso/issues/46496)
  • __experimentalTreeGridItem (unused)
  • __experimentalTreeGridRow (used, see https://github.com/Automattic/wp-calypso/issues/46496)

Block API

  • __experimentalGetAccessibleBlockLabel (unused)
  • __experimentalGetBlockLabel (unused)
Was this page helpful?
0 / 5 - 0 ratings