wppaste
WordPress

WP_REST_Request::parse_json_params(): true|WP_Error

Since
4.4.0, 4.7.0
Source
wp-includes/rest-api/class-wp-rest-request.php:703
Parses the JSON parameters.

Description

Avoids parsing the JSON data until we need to access it.

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

true|WP_Error
True if the JSON data was passed or no JSON data was provided, WP_Error if invalid JSON was passed.

Performance profile

How much work a call to WP_REST_Request::parse_json_params() 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
3–43

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
3

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

What it touches

  • serializeserialisationjson_decode()called directly

Further down the call graph this can also reach hook, query, option, cache and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 6 distinct outcomes

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

WhenInstructionsCalls it makes
always3none
!->is_json_content_type()8->is_json_content_type()
->is_json_content_type() && empty($body)13->is_json_content_type(), ->get_body()
->is_json_content_type() && !empty($body) && $params !== null23->is_json_content_type(), ->get_body(), json_decode()
->is_json_content_type() && !empty($body) && $params === null27->is_json_content_type(), ->get_body(), json_decode(), json_last_error()
->is_json_content_type() && !empty($body) && $params === null43->is_json_content_type(), ->get_body(), json_decode(), json_last_error(), json_last_error(), json_last_error_msg(), __(), status()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 50 instructions, 3–43 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 · 4

Used by · 3

Source code

	protected function parse_json_params() {		if ( $this->parsed_json ) {			return true;		} 		$this->parsed_json = true; 		// Check that we actually got JSON.		if ( ! $this->is_json_content_type() ) {			return true;		} 		$body = $this->get_body();		if ( empty( $body ) ) {			return true;		} 		$params = json_decode( $body, true ); 		/*		 * Check for a parsing error.		 */		if ( null === $params && JSON_ERROR_NONE !== json_last_error() ) {			// Ensure subsequent calls receive error instance.			$this->parsed_json = false; 			$error_data = array(				'status'             => WP_Http::BAD_REQUEST,				'json_error_code'    => json_last_error(),				'json_error_message' => json_last_error_msg(),			); 			return new WP_Error( 'rest_invalid_json', __( 'Invalid JSON body passed.' ), $error_data );		} 		$this->params['JSON'] = $params; 		return true;	}

Changelog

Introduced in 4.4.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.

4.7.0
Returns error instance if value cannot be decoded.from the docblock
4.4.0
Introduced.from the docblock

About this page

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