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 |
---|---|
1059 | } |
1060 |
|
1061 | /** |
1062 | * Filters the REST endpoint data. |
1063 | * |
1064 | * @since 4.4.0 |
1065 | * |
1066 | * @param WP_REST_Request $request Request data. The namespace is passed as the 'namespace' parameter. |
1067 | */ |
1068 | $available[ $route ] = apply_filters( 'rest_endpoints_description', $data ); |
1069 | } |
1070 |
|
1071 | /** |
1072 | * Filters the publicly-visible data for routes. |
1073 | * |
1074 | * This data is exposed on indexes and can be used by clients or |
1075 | * developers to investigate the site and find out how to use it. It |
1076 | * acts as a form of self-documentation. |
1077 | * |