WP_Theme_JSON_Resolver::resolve_theme_file_uris( WP_Theme_JSON $theme_json ): WP_Theme_JSON
- Since
- 6.6.0
- Source
wp-includes/class-wp-theme-json-resolver.php:922
Compatibility
- WordPress
- since 6.6.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
$theme_jsonWP_Theme_JSON- A theme json instance.
Return value
WP_Theme_JSON- Theme merged with resolved paths, if any found.
Performance profile
How much work a call to WP_Theme_JSON_Resolver::resolve_theme_file_uris() 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
- Scaling
- Scales with input
- Instructions
- 8–17
- Plugin surface
- None
- Called by
- 2
Touches nothing outside its own arguments.
The body loops, so the work grows with what you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 32.
Nothing here hands control to plugin code.
2 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 WP_Theme_JSON_Resolver::resolve_theme_file_uris() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
empty($resolved_urls) | 8 | ::get_resolved_theme_uris() |
!empty($resolved_urls) | 16–17 | ::get_resolved_theme_uris(), ->get_raw_data() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 32 instructions, 8–17 executed per call, 3 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
- _wp_array_set()Sets an array in depth based on a path of keys.
- static::get_resolved_theme_uris()
- WP_Theme_JSON::__construct()Constructor.
Used by · 2
- wp_add_global_styles_for_blocks()Adds global style rules to the inline style for each block.
- wp_get_global_stylesheet()Returns the stylesheet resulting of merging core, theme, and user data.
Source code
public static function resolve_theme_file_uris( $theme_json ) { $resolved_urls = static::get_resolved_theme_uris( $theme_json ); if ( empty( $resolved_urls ) ) { return $theme_json; } $resolved_theme_json_data = $theme_json->get_raw_data(); foreach ( $resolved_urls as $resolved_url ) { $path = explode( '.', $resolved_url['target'] ); _wp_array_set( $resolved_theme_json_data, $path, $resolved_url['href'] ); } return new WP_Theme_JSON( $resolved_theme_json_data ); }Changelog
Introduced in 6.6.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-theme-json-resolver.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.