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 |
|---|---|
| 931 | * |
| 932 | * @since 4.4.0 |
| 933 | * @since 4.5.0 Added `$route` and `$handler` parameters. |
| 934 | * |
| 935 | * @param mixed $dispatch_result Dispatch result, will be used if not empty. |
| 936 | * @param WP_REST_Request $request Request used to generate the response. |
| 937 | * @param string $route Route matched for the request. |
| 938 | * @param array $handler Route handler used for the request. |
| 939 | */ |
| 940 | $dispatch_result = apply_filters( 'rest_dispatch_request', null, $request, $route, $handler ); |
| 941 | |
| 942 | // Allow plugins to halt the request via this filter. |
| 943 | if ( null !== $dispatch_result ) { |
| 944 | $response = $dispatch_result; |
| 945 | } else { |
| 946 | $response = call_user_func( $callback, $request ); |
| 947 | } |
| 948 | } |
| 949 | |