WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 2338 | |
| 2339 | /** |
| 2340 | * Filters the flag that decides whether or not block editor scripts and styles |
| 2341 | * are going to be enqueued on the current screen. |
| 2342 | * |
| 2343 | * @since 5.6.0 |
| 2344 | * |
| 2345 | * @param bool $is_block_editor_screen Current value of the flag. |
| 2346 | */ |
| 2347 | return apply_filters( 'should_load_block_editor_scripts_and_styles', $is_block_editor_screen ); |
| 2348 | } |
| 2349 | |
| 2350 | /** |
| 2351 | * Checks whether separate styles should be loaded for core blocks on-render. |
| 2352 | * |
| 2353 | * When this function returns true, other functions ensure that core blocks |
| 2354 | * only load their assets on-render, and each block loads its own, individual |
| 2355 | * assets. Third-party blocks only load their assets when rendered. |
| 2356 | * |