WP_REST_Menus_Controller::prepare_links( WP_Term $term ): array
- Since
- 5.9.0
- Source
wp-includes/rest-api/endpoints/class-wp-rest-menus-controller.php:160
Compatibility
- WordPress
- since 5.9.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Parameters
$termWP_Term- Term object.
Return value
array- Links for the given term.
Performance profile
How much work a call to WP_REST_Menus_Controller::prepare_links() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.
- Cost class
- Light
- Scaling
- Scales with input
- Instructions
- 14–15
- Plugin surface
- None
- Called by
- 1
Touches nothing outside its own arguments.
The body loops, so the work grows with what you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 26.
Nothing here hands control to plugin code.
1 place in core call this, so the cost is paid more often than your own code shows.
What one call costs · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_REST_Menus_Controller::prepare_links() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 14–15 | ::prepare_links(), ->get_menu_locations() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 26 | 14–15 | 2 | |
| 8.5 | 26 | 14–15 | 2 | |
| 8.4 | 26 | 14–15 | 2 | 3 fewer instructions than PHP 8.3 |
| 8.3 | 29 | 14–15 | 2 | |
| 8.2 | 29 | 14–15 | 2 | |
| 8.1 | 29 | 14–15 | 2 | |
| 7.4 | 29 | 14–15 | 2 |
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Uses · 3
- rest_url()Retrieves the URL to a REST endpoint.
- WP_REST_Terms_Controller::prepare_links()Prepares links for the request.
- WP_REST_Menus_Controller::get_menu_locations()Returns the names of the locations assigned to the menu.
Used by · 1
- WP_REST_Menus_Controller::prepare_item_for_response()Prepares a single term output for response.
Source code
protected function prepare_links( $term ) { $links = parent::prepare_links( $term ); $locations = $this->get_menu_locations( $term->term_id ); foreach ( $locations as $location ) { $url = rest_url( sprintf( 'wp/v2/menu-locations/%s', $location ) ); $links['https://api.w.org/menu-location'][] = array( 'href' => $url, 'embeddable' => true, ); } return $links; }Changelog
Introduced in 5.9.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/rest-api/endpoints/class-wp-rest-menus-controller.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it. - Corrections
- Something wrong on this page? Report it and it gets fixed in the next regeneration.