wppaste
WordPress

WP_REST_Revisions_Controller::get_item_schema(): array

Since
4.7.0
Source
wp-includes/rest-api/endpoints/class-wp-rest-revisions-controller.php:723
Retrieves the revision's schema, conforming to JSON Schema.

Compatibility

WordPress
since 4.7.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.

Return value

array
Item schema data.

Performance profile

How much work a call to WP_REST_Revisions_Controller::get_item_schema() 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
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
8–126

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 132.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_REST_Revisions_Controller::get_item_schema() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always8->add_additional_fields_schema()
always106–126__(), __(), __(), __(), __(), __(), __(), __(), __(), ->get_item_schema(), ->get_field_schema(), ->add_additional_fields_schema()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 132 instructions, 8–126 executed per call, 5 branches. The work does not change between versions.

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 · 2

  • __()Retrieves the translation of $text.
  • WP_REST_Revisions_Controller::add_additional_fields_schema()

Used by · 1

Source code

	public function get_item_schema() {		if ( $this->schema ) {			return $this->add_additional_fields_schema( $this->schema );		} 		$schema = array(			'$schema'    => 'http://json-schema.org/draft-04/schema#',			'title'      => "{$this->parent_post_type}-revision",			'type'       => 'object',			// Base properties for every Revision.			'properties' => array(				'author'       => array(					'description' => __( 'The ID for the author of the revision.' ),					'type'        => 'integer',					'context'     => array( 'view', 'edit', 'embed' ),				),				'date'         => array(					'description' => __( "The date the revision was published, in the site's timezone." ),					'type'        => 'string',					'format'      => 'date-time',					'context'     => array( 'view', 'edit', 'embed' ),				),				'date_gmt'     => array(					'description' => __( 'The date the revision was published, as GMT.' ),					'type'        => 'string',					'format'      => 'date-time',					'context'     => array( 'view', 'edit' ),				),				'guid'         => array(					'description' => __( 'GUID for the revision, as it exists in the database.' ),					'type'        => 'string',					'context'     => array( 'view', 'edit' ),				),				'id'           => array(					'description' => __( 'Unique identifier for the revision.' ),					'type'        => 'integer',					'context'     => array( 'view', 'edit', 'embed' ),				),				'modified'     => array(					'description' => __( "The date the revision was last modified, in the site's timezone." ),					'type'        => 'string',					'format'      => 'date-time',					'context'     => array( 'view', 'edit' ),				),				'modified_gmt' => array(					'description' => __( 'The date the revision was last modified, as GMT.' ),					'type'        => 'string',					'format'      => 'date-time',					'context'     => array( 'view', 'edit' ),				),				'parent'       => array(					'description' => __( 'The ID for the parent of the revision.' ),					'type'        => 'integer',					'context'     => array( 'view', 'edit', 'embed' ),				),				'slug'         => array(					'description' => __( 'An alphanumeric identifier for the revision unique to its type.' ),					'type'        => 'string',					'context'     => array( 'view', 'edit', 'embed' ),				),			),		); 		$parent_schema = $this->parent_controller->get_item_schema(); 		if ( ! empty( $parent_schema['properties']['title'] ) ) {			$schema['properties']['title'] = $parent_schema['properties']['title'];		} 		if ( ! empty( $parent_schema['properties']['content'] ) ) {			$schema['properties']['content'] = $parent_schema['properties']['content'];		} 		if ( ! empty( $parent_schema['properties']['excerpt'] ) ) {			$schema['properties']['excerpt'] = $parent_schema['properties']['excerpt'];		} 		if ( ! empty( $parent_schema['properties']['guid'] ) ) {			$schema['properties']['guid'] = $parent_schema['properties']['guid'];		}

Changelog

Introduced in 4.7.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 6.9.7 tag, from src/wp-includes/rest-api/endpoints/class-wp-rest-revisions-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.