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 |
---|---|
1376 | * This data is exposed on indexes and can be used by clients or |
1377 | * developers to investigate the site and find out how to use it. It |
1378 | * acts as a form of self-documentation. |
1379 | * |
1380 | * @since 4.4.0 |
1381 | * |
1382 | * @param array[] $available Route data to expose in indexes, keyed by route. |
1383 | * @param array $routes Internal route data as an associative array. |
1384 | */ |
1385 | return apply_filters( 'rest_route_data', $available, $routes ); |
1386 | } |
1387 |
|
1388 | /** |
1389 | * Retrieves publicly-visible data for the route. |
1390 | * |
1391 | * @since 4.4.0 |
1392 | * |
1393 | * @param string $route Route to get data for. |
1394 | * @param array $callbacks Callbacks to convert to data. |