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 |
---|---|
1124 | * This data is exposed on indexes and can be used by clients or |
1125 | * developers to investigate the site and find out how to use it. It |
1126 | * acts as a form of self-documentation. |
1127 | * |
1128 | * @since 4.4.0 |
1129 | * |
1130 | * @param array $available Map of route to route data. |
1131 | * @param array $routes Internal route data as an associative array. |
1132 | */ |
1133 | return apply_filters( 'rest_route_data', $available, $routes ); |
1134 | } |
1135 |
|
1136 | /** |
1137 | * Retrieves publicly-visible data for the route. |
1138 | * |
1139 | * @since 4.4.0 |
1140 | * @access public |
1141 | * |
1142 | * @param string $route Route to get data for. |