WP_Duotone::get_global_styles_presets( array $sources ): string
- Since
- 6.3.0, 6.6.0
- Source
wp-includes/class-wp-duotone.php:825
Description
Example output: body{--wp--preset--duotone--blue-orange:url('#wp-duotone-blue-orange');}
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
$sourcesarray- The duotone presets.
Return value
string- The CSS for global styles.
Performance profile
How much work a call to WP_Duotone::get_global_styles_presets() 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
- Scales with input
- Instructions
- 7–8
- Plugin surface
- None
- Called by
- 3
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.
3 places 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_Duotone::get_global_styles_presets() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 7–8 | none |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 31 | 7–8 | 3 | 1 fewer instruction than PHP 8.5 |
| 8.5 | 32 | 7–8 | 3 | |
| 8.4 | 32 | 7–8 | 3 | |
| 8.3 | 32 | 7–8 | 3 | |
| 8.2 | 32 | 7–8 | 3 | |
| 8.1 | 32 | 7–8 | 3 | |
| 7.4 | 32 | 7–8 | 3 |
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 · 2
- WP_Duotone::get_css_custom_property_name()Gets the CSS variable name for a duotone preset.
- WP_Duotone::get_filter_url()Get the URL for a duotone filter.
Used by · 3
- WP_Duotone::add_editor_settings()Adds the duotone SVGs and CSS custom properties to the editor settings.
- WP_Duotone::output_footer_assets()Outputs all necessary SVG for duotone filters, CSS for classic themes.
- WP_Duotone::output_global_styles()Appends the used global style duotone filter presets (CSS custom properties) to the inline global styles CSS.
Source code
private static function get_global_styles_presets( $sources ) { $css = WP_Theme_JSON::ROOT_CSS_PROPERTIES_SELECTOR . '{'; foreach ( $sources as $filter_id => $filter_data ) { $slug = $filter_data['slug']; $colors = $filter_data['colors']; $css_property_name = self::get_css_custom_property_name( $slug ); $declaration_value = is_string( $colors ) ? $colors : self::get_filter_url( $filter_id ); $css .= "$css_property_name:$declaration_value;"; } $css .= '}'; return $css; }Changelog
Introduced in 6.3.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
WP_Theme_JSON::ROOT_CSS_PROPERTIES_SELECTOR.from the docblockAbout this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-duotone.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.