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 |
|---|---|
| 280 | * |
| 281 | * Well-behaved clients should expand and normalise these back to their |
| 282 | * full URI relation, however some naive clients may not resolve these |
| 283 | * correctly, so adding new CURIEs may break backward compatibility. |
| 284 | * |
| 285 | * @since 4.5.0 |
| 286 | * |
| 287 | * @param array $additional Additional CURIEs to register with the REST API. |
| 288 | */ |
| 289 | $additional = apply_filters( 'rest_response_link_curies', array() ); |
| 290 | |
| 291 | return array_merge( $curies, $additional ); |
| 292 | } |
| 293 | } |
| 294 | |