wppaste
WordPress

WP_Style_Engine_Processor::add_rules( WP_Style_Engine_CSS_Rule|WP_Style_Engine_CSS_Rule[] $css_rules ): WP_Style_Engine_Processor

Since
6.1.0, 6.6.0
Source
wp-includes/style-engine/class-wp-style-engine-processor.php:68
Adds rules to be processed.

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

$css_rulesWP_Style_Engine_CSS_Rule|WP_Style_Engine_CSS_Rule[]
A single, or an array of, WP_Style_Engine_CSS_Rule objects from a store or otherwise.

Return value

WP_Style_Engine_Processor
Returns the object to allow chaining methods.

Performance profile

How much work a call to WP_Style_Engine_Processor::add_rules() 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
Scales with input

The body loops, so the work grows with what you pass in.

Instructions
7–10

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
1

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_Style_Engine_Processor::add_rules() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always7–10none

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 59 instructions, 7–10 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.

Used by · 1

Source code

	public function add_rules( $css_rules ) {		if ( ! is_array( $css_rules ) ) {			$css_rules = array( $css_rules );		} 		foreach ( $css_rules as $rule ) {			$selector    = $rule->get_selector();			$rules_group = $rule->get_rules_group(); 			/**			 * If there is a rules_group and it already exists in the css_rules array,			 * add the rule to it.			 * Otherwise, create a new entry for the rules_group.			 */			if ( ! empty( $rules_group ) ) {				if ( isset( $this->css_rules[ "$rules_group $selector" ] ) ) {					$this->css_rules[ "$rules_group $selector" ]->add_declarations( $rule->get_declarations() );					continue;				}				$this->css_rules[ "$rules_group $selector" ] = $rule;				continue;			} 			// If the selector already exists, add the declarations to it.			if ( isset( $this->css_rules[ $selector ] ) ) {				$this->css_rules[ $selector ]->add_declarations( $rule->get_declarations() );				continue;			}			$this->css_rules[ $rule->get_selector() ] = $rule;		} 		return $this;	}

Changelog

Introduced in 6.1.0. Unchanged from 6.7.7 through 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.

6.6.0
Added support for rules_group.from the docblock
6.1.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-includes/style-engine/class-wp-style-engine-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.