wpseek.com
A WordPress-centric search engine for devs and theme authors



wp_should_load_separate_core_block_assets › WordPress Function

Since5.8.0
Deprecatedn/a
› wp_should_load_separate_core_block_assets ( No parameters )
See:
Returns:
  • (bool) Whether separate assets will be loaded.
Defined at:
Codex:

Checks whether separate styles should be loaded for core blocks on-render.

When this function returns true, other functions ensure that core blocks only load their assets on-render, and each block loads its own, individual assets. Third-party blocks only load their assets when rendered. When this function returns false, all core block assets are loaded regardless of whether they are rendered in a page or not, because they are all part of the block-library/style.css file. Assets for third-party blocks are always enqueued regardless of whether they are rendered or not. This only affects front end and not the block editor screens.


Related Functions: _load_remote_block_patterns, wp_should_upgrade_global_tables, wp_should_load_block_editor_scripts_and_styles, build_template_part_block_variations, wp_should_replace_insecure_home_url

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 );
}