Rachel Baker

Display a message of some sort if the `WP_REST_Posts_Controller` does not exist, instead of just returning early.

Improve downloading/installation instructions in Step 0 of Readme

5

At least add a link to the WP-CLI packages installation instructions: https://github.com/wp-cli/wp-cli/wiki/Community-Packages

Add /batch GET endpoint

5

Based on feedback from the Automattic team (shared by @pento): > /batch > The /batch endpoint encourages apps written for the WP.com to be efficient with round trips. For example,...

On Comment POST/PUT return WP_Error for strings that exceed the DB column size

2

Mimic the logic in `wp_handle_comment_submission()` to use `wp_get_comment_fields_max_lengths()` and return the appropriate error for 'comment_author', 'comment_author_email', 'comment_author_url', or 'comment_content' strings that exceed the maximum length of their column in the...

Return an error instead of ignoring `readonly` properties

4

In 0e8364ea5c59a9ce03a85c243c690101a5213c2f we only ignore any request params that should be `readonly`, and continue to process the request. This means values that were expected to be set or updated are...

Change the `post_title` database sanitization function to`wp_filter_kses()`

2

We should match WordPress Core's sanitization function when adding/updating the title of a Post. WordPress Core uses [`wp_filter_kses()`](https://core.trac.wordpress.org/browser/trunk/src/wp-includes/kses.php#L1625) but we use [`wp_filter_post_kses()`](https://github.com/WP-API/WP-API/blob/develop/lib/endpoints/class-wp-rest-posts-controller.php#L804).

Modify the schema to apply callbacks or required parameters to nested objects

2

Allow schema properties like `sanitization_callback`, `type`, `required`, etc. to be set and processed on nested objects. Currently `rest_sanitize_request_arg()` and `rest_validate_request_arg()` only handle properties set on the top level of nested...