Daniel Bachhuber
Daniel Bachhuber
Because each endpoint is more or less the same, we should have an abstraction for running the same tests against all types of meta endpoints.
Given our JSON schema definition includes attributes not present in draft v4, we need to eventually publish our derivative.
Three important use cases for WordPress.com: - Assign Categories and Tags when creating a new Post. - Upload an Attachment when creating a New Post. - Create and insert a...
Throughout the codebase, we have static strings like 'Sorry, you are not allowed to create new posts.' and "The date the object was published, in the site's timezone.". Generally, strings...
On multisite, it should be possible to permanently delete a user from the network. To do so, we'll need to use `wpmu_delete_user()`, as `wp_delete_user()` simply removes capabilities on multisite. Related...
It's new and shiny as of 4.6. We should be able to remove `WP_REST_Terms_Controller->get_terms_for_post()` in the process.
To avoid obtuse computer language like this:  It would be nice if we could create human-readable descriptions for each endpoint.
Let's make sure they're consistent across the board.
We currently have one `comments` endpoint which handles multiple comment types. Similar to how we have `/wp/v2/posts` and `/wp/v2/pages`, we should create `/wp/v2/pingbacks` (and other endpoints, for other comment types)....
Just like we have type checks for `string` and `integer`, we should also have a type check for `array`. However, when we do this, we'll need to address instances where...