WP_Block_Bindings_Source::get_value( array $source_args, WP_Block $block_instance, string $attribute_name ): mixed
- Since
- 6.5.0, 6.7.0
- Source
wp-includes/class-wp-block-bindings-source.php:85
$get_value_callback property with the given arguments and returns the result. It can be modified with block_bindings_source_value filter.Compatibility
- WordPress
- since 6.7.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
$source_argsarray- Array containing source arguments used to look up the override value, i.e. {"key": "foo"}.
$block_instanceWP_Block- The block instance.
$attribute_namestring- The name of the target attribute.
Return value
mixed- The value of the source.
Performance profile
How much work a call to WP_Block_Bindings_Source::get_value() 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
- 23
- Plugin surface
- 1 hook
- Called by
- 0
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 23.
Third-party callbacks on 'block_bindings_source_value' run inside this call, and their cost is not bounded by anything here.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
apply_filters()called directly
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_Bindings_Source::get_value() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 23 | apply_filters() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 23 | 23 | 0 | |
| 8.5 | 23 | 23 | 0 | |
| 8.4 | 23 | 23 | 0 | |
| 8.3 | 23 | 23 | 0 | |
| 8.2 | 23 | 23 | 0 | |
| 8.1 | 23 | 23 | 0 | 1 more instruction than PHP 7.4 |
| 7.4 | 22 | 22 | 0 |
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.
Hooks and filters fired · 1
One hook fires while WP_Block_Bindings_Source::get_value() runs, in this order:
- apply_filters( block_bindings_source_value )filterline 98 (+13 into the body)
Filters the output of a block bindings source.
Uses · 1
- apply_filters()Calls the callback functions that have been added to a filter hook.
Source code
public function get_value( array $source_args, $block_instance, string $attribute_name ) { $value = call_user_func_array( $this->get_value_callback, array( $source_args, $block_instance, $attribute_name ) ); /** * Filters the output of a block bindings source. * * @since 6.7.0 * * @param mixed $value The computed value for the source. * @param string $name The name of the source. * @param array $source_args Array containing source arguments used to look up the override value, i.e. { "key": "foo" }. * @param WP_Block $block_instance The block instance. * @param string $attribute_name The name of an attribute. */ return apply_filters( 'block_bindings_source_value', $value, $this->name, $source_args, $block_instance, $attribute_name ); }Changelog
Introduced in 6.5.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
block_bindings_source_value filter was added.from the docblockAbout this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-block-bindings-source.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.