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 |
---|---|
2179 | * Fires after enqueuing block assets for both editor and front-end. |
2180 | * |
2181 | * Call `add_action` on any hook before 'wp_enqueue_scripts'. |
2182 | * |
2183 | * In the function call you supply, simply use `wp_enqueue_script` and |
2184 | * `wp_enqueue_style` to add your functionality to the Gutenberg editor. |
2185 | * |
2186 | * @since 5.0.0 |
2187 | */ |
2188 | do_action( 'enqueue_block_assets' ); |
2189 | } |
2190 |
|
2191 | /** |
2192 | * Checks if the editor scripts and styles for all registered block types |
2193 | * should be enqueued on the current screen. |
2194 | * |
2195 | * @since 5.6.0 |
2196 | * |
2197 | * @return bool |