wppaste
WordPress

wp_migrate_old_typography_shape( array $metadata ): array

Since
5.8.0
Source
wp-includes/blocks.php:2639
Converts typography keys declared under supports.* to supports.typography.*.

Description

Displays a _doing_it_wrong() notice when a block using the older format is detected.

Compatibility

WordPress
since 5.8.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$metadataarray
Metadata for registering a block type.

Return value

array
Filtered metadata for registering a block type.

Performance profile

How much work a call to wp_migrate_old_typography_shape() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Light

Touches nothing outside its own arguments.

Scaling
Scales with input

The body loops, so the work grows with what you pass in.

Instructions
4–7

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 53.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

  • hookthird-party callbacksdo_action()one call below wp_migrate_old_typography_shape()

Further down the call graph this can also reach query, option, cache, serialize and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_migrate_old_typography_shape() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always4–7none

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 53 instructions, 4–7 executed per call, 5 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 3

Source code

function wp_migrate_old_typography_shape( $metadata ) {	if ( ! isset( $metadata['supports'] ) ) {		return $metadata;	} 	$typography_keys = array(		'__experimentalFontFamily',		'__experimentalFontStyle',		'__experimentalFontWeight',		'__experimentalLetterSpacing',		'__experimentalTextDecoration',		'__experimentalTextTransform',		'fontSize',		'lineHeight',	); 	foreach ( $typography_keys as $typography_key ) {		$support_for_key = $metadata['supports'][ $typography_key ] ?? null; 		if ( null !== $support_for_key ) {			_doing_it_wrong(				'register_block_type_from_metadata()',				sprintf(					/* translators: 1: Block type, 2: Typography supports key, e.g: fontSize, lineHeight, etc. 3: block.json, 4: Old metadata key, 5: New metadata key. */					__( 'Block "%1$s" is declaring %2$s support in %3$s file under %4$s. %2$s support is now declared under %5$s.' ),					$metadata['name'],					"<code>$typography_key</code>",					'<code>block.json</code>',					"<code>supports.$typography_key</code>",					"<code>supports.typography.$typography_key</code>"				),				'5.8.0'			); 			_wp_array_set( $metadata['supports'], array( 'typography', $typography_key ), $support_for_key );			unset( $metadata['supports'][ $typography_key ] );		}	} 	return $metadata;}

Changelog

Introduced in 5.8.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 7.0.4 tag, from src/wp-includes/blocks.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.