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 |
|---|---|
| 1156 | * |
| 1157 | * @since 4.4.0 |
| 1158 | * @since 4.5.0 Added `$route` and `$handler` parameters. |
| 1159 | * |
| 1160 | * @param mixed $dispatch_result Dispatch result, will be used if not empty. |
| 1161 | * @param WP_REST_Request $request Request used to generate the response. |
| 1162 | * @param string $route Route matched for the request. |
| 1163 | * @param array $handler Route handler used for the request. |
| 1164 | */ |
| 1165 | $dispatch_result = apply_filters( 'rest_dispatch_request', null, $request, $route, $handler ); |
| 1166 | |
| 1167 | // Allow plugins to halt the request via this filter. |
| 1168 | if ( null !== $dispatch_result ) { |
| 1169 | $response = $dispatch_result; |
| 1170 | } else { |
| 1171 | $response = call_user_func( $handler['callback'], $request ); |
| 1172 | } |
| 1173 | } |
| 1174 | |