WP_Block_Processor::opens_block( string[] $block_type ): bool
- Since
- 6.9.0
- Source
wp-includes/class-wp-block-processor.php:1581
Description
This is a helper method to ease handling of code inspecting where blocks start, and for checking if the blocks are of a given type. The function is variadic to allow for checking if the delimiter opens one of many possible block types.
To advance to the start of a block self::next_block().
Example:
$processor = new WP_Block_Processor( $html );
while ( $processor->next_delimiter() ) {
if ( $processor->opens_block( 'core/code', 'syntaxhighlighter/code' ) ) {
echo "Found code!";
continue;
}
if ( $processor->opens_block( 'core/image' ) ) {
echo "Found an image!";
continue;
}
if ( $processor->opens_block() ) {
echo "Found a new block!";
}
}Compatibility
- WordPress
- since 6.9.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in 3 of the 5 tracked releases, added in 6.9.0, and compiles on PHP 7.4 through 8.6-dev.
Parameters
$block_typestring[]- Is the matched block type one of these? If none are provided, will not test block type.
Return value
bool- Whether the matched block delimiter opens a block, and whether it opens a block of one of the given block types, if provided.
Performance profile
How much work a call to WP_Block_Processor::opens_block() 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
- Scaling
- Constant
- Instructions
- 5
- Plugin surface
- None
- Called by
- 1
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 33.
Nothing here hands control to plugin code.
1 place in core call this, so the cost is paid more often than your own code shows.
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_Block_Processor::opens_block() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 5 | ->is_block_type() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 33 | 5 | 5 | |
| 8.5 | 33 | 5 | 5 | |
| 8.4 | 33 | 5 | 5 | 2 fewer instructions than PHP 8.3 |
| 8.3 | 35 | 6 | 5 | |
| 8.2 | 35 | 6 | 5 | |
| 8.1 | 35 | 6 | 5 | 6 more instructions than PHP 7.4 |
| 7.4 | 29 | 10–26 | 5 |
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
- array_any()Polyfill for `array_any()` function added in PHP 8.4.
- WP_Block_Processor::is_html()Indicates if the matched delimiter is an HTML span.
- WP_Block_Processor::is_block_type()Indicates if the block delimiter represents a block of the given type.
Used by · 1
- WP_Block_Processor::extract_full_block_and_advance()Extracts a block object, and all inner content, starting at a matched opening block delimiter, or at a matched top-level HTML span as freeform HTML content.
Source code
public function opens_block( string ...$block_type ): bool { // HTML spans only open implicit freeform content at the top level. if ( self::HTML_SPAN === $this->state && 1 !== count( $this->open_blocks_at ) ) { return false; } /* * Because HTML spans are discovered after the next delimiter is found, * the delimiter type when visiting HTML spans refers to the type of the * following delimiter. Therefore the HTML case is handled by checking * the state and depth of the stack of open block. */ if ( self::CLOSER === $this->type && ! $this->is_html() ) { return false; } if ( count( $block_type ) === 0 ) { return true; } return array_any( $block_type, fn( $block ) => $this->is_block_type( $block ) ); }Changelog
Introduced in 6.9.0. Unchanged from 6.9.7 through 7.1.0.
Signature, return type and hooks compared across 3 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-block-processor.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.