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 |
---|---|
293 | * |
294 | * Well-behaved clients should expand and normalise these back to their |
295 | * full URI relation, however some naive clients may not resolve these |
296 | * correctly, so adding new CURIEs may break backward compatibility. |
297 | * |
298 | * @since 4.5.0 |
299 | * |
300 | * @param array $additional Additional CURIEs to register with the API. |
301 | */ |
302 | $additional = apply_filters( 'rest_response_link_curies', array() ); |
303 | return array_merge( $curies, $additional ); |
304 | } |
305 | } |
306 |
|