wppaste
WordPress

block_has_support( WP_Block_Type $block_type, string|array $feature, mixed $default_value = false ): bool

Since
5.8.0, 6.4.0
Source
wp-includes/blocks.php:2522
Checks whether the current block type supports the feature requested.

Compatibility

WordPress
since 6.4.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

$block_typeWP_Block_Type
Block type to check for support.
$featurestring|array
Feature slug, or path to a specific feature to check support for.
$default_valuemixedoptional
Fallback value for feature support. Default false.Default: false

Return value

bool
Whether the feature is supported.

Performance profile

How much work a call to block_has_support() 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
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
9–28

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
28

28 places in core call this, so the cost is paid more often than your own code shows.

What one call costs · 2 distinct outcomes

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

WhenInstructionsCalls it makes
always9–25none
$block_type instanceof && is_array($feature)22–28_wp_array_get()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 34 instructions, 9–28 executed per call, 6 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 · 1

Used by · 28

Show all 28

Source code

function block_has_support( $block_type, $feature, $default_value = false ) {	$block_support = $default_value;	if ( $block_type instanceof WP_Block_Type ) {		if ( is_array( $feature ) && count( $feature ) === 1 ) {			$feature = $feature[0];		} 		if ( is_array( $feature ) ) {			$block_support = _wp_array_get( $block_type->supports, $feature, $default_value );		} elseif ( isset( $block_type->supports[ $feature ] ) ) {			$block_support = $block_type->supports[ $feature ];		}	} 	return true === $block_support || is_array( $block_support );}

Changelog

Introduced in 5.8.0. One change between 6.7.7 and 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.

7.0.4
Parameter $block_type retyped from WP_Block_Type to WP_Block_Type|null.verified against source
6.4.0
The $feature parameter now supports a string.from the docblock
5.8.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 6.8.8 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.