wppaste
WordPress

wp_should_load_separate_core_block_assets(): bool

Since
5.8.0
Source
wp-includes/script-loader.php:2614
Checks whether separate styles should be loaded for core blocks.

Description

When this function returns true, other functions ensure that core blocks use their own separate stylesheets.
When this function returns false, all core blocks will use the single combined 'wp-block-library' stylesheet.

As a side effect, the return value will by default result in block assets to be loaded on demand, via the wp_should_load_block_assets_on_demand() function. This behavior can be separately altered via that function.

This only affects front end and not the block editor screens.

Return

bool
Whether separate core block assets will be loaded.

Cost profile

Measured from the compiled opcodes, not from a stopwatch. Every number here is identical on any machine that runs the same PHP version, and every function in core is ranked by these figures.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
4–14

Executed per call on PHP 8.4, depending on the branch taken. The body compiles to 15.

Plugin surface
1 hook

Third-party callbacks on 'should_load_separate_core_block_assets' run inside this call, and their cost is not bounded by anything here.

Called by
6

6 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

Further down the call graph this can also reach query, option, cache, serialize and transient those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 4 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_should_load_separate_core_block_assets() can have, taken from its control-flow graph on PHP 8.4.

WhenInstructionsCalls it makes
is_admin()4is_admin()
!is_admin() && is_feed()7is_admin()is_feed()
!is_admin() && !is_feed() && wp_is_rest_endpoint()10is_admin()is_feed()wp_is_rest_endpoint()
!is_admin() && !is_feed() && !wp_is_rest_endpoint()14is_admin()is_feed()wp_is_rest_endpoint()apply_filters()

Across PHP versions

PHPCompiledExecutedBranchesNotes
7.4154–143Compiles to the same instructions
8.1154–143Compiles to the same instructions
8.2154–143Compiles to the same instructions
8.3154–143Compiles to the same instructions
8.4154–143Compiles to the same instructions

Oldest PHP that compiles this body: 7.4. An instruction is not a fixed amount of time, so a version with the same count is not necessarily the same speed; what the count rules out is a difference in the work itself.

Hooks fired · 1

One hook fires while wp_should_load_separate_core_block_assets() runs, in this order:

  1. apply_filters( should_load_separate_core_block_assets )filterline 2630 (+16 into the body)

    Filters whether block styles should be loaded separately.

Uses · 4

  • is_admin()Determines whether the current request is for an administrative interface page.
  • is_feed()Determines whether the query is for a feed.
  • wp_is_rest_endpoint()Checks whether a REST API endpoint request is currently being handled.
  • apply_filters()Calls the callback functions that have been added to a filter hook.

Used by · 6

Source

function wp_should_load_separate_core_block_assets() {	if ( is_admin() || is_feed() || wp_is_rest_endpoint() ) {		return false;	} 	/**	 * Filters whether block styles should be loaded separately.	 *	 * Returning false loads all core block assets, regardless of whether they are rendered	 * in a page or not. Returning true loads core block assets only when they are rendered.	 *	 * @since 5.8.0	 *	 * @param bool $load_separate_assets Whether separate assets will be loaded.	 *                                   Default false (all block assets are loaded, even when not used).	 */	return apply_filters( 'should_load_separate_core_block_assets', false );}

History

Introduced in 5.8.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.

About this page

Parsed data
Generated from the wordpress-develop 6.8.8 tag, from src/wp-includes/script-loader.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.