Implement new-style meta with register_meta

.travis.yml

@@ -9,10 +9,10 @@ matrix:
   include:
   - php: 5.6
     env: WP_TRAVISCI=travis:phpunit WP_VERSION=nightly
-  - php: 5.6
-    env: WP_TRAVISCI=travis:phpunit WP_VERSION=latest
   - php: 5.6
     env: WP_TRAVISCI=travis:phpvalidate
+  - php: 5.6
+    env: WP_TRAVISCI=travis:codecoverage
   - php: 5.5
     env: WP_TRAVISCI=travis:phpunit WP_VERSION=nightly
   - php: 5.4

README.md

@@ -1,21 +1,62 @@
-# WP REST API Meta Endpoints #
-**Contributors:** rmccue, rachelbaker, danielbachhuber, joehoyle  
-**Tags:** json, rest, api, rest-api  
-**Requires at least:** 4.4  
-**Tested up to:** 4.5-alpha  
-**Stable tag:** 0.1.0  
-**License:** GPLv2 or later  
-**License URI:** http://www.gnu.org/licenses/gpl-2.0.html  
+# WP REST API - Meta Support
 
-WP REST API companion plugin for post meta endpoints.
+[![Build Status](https://travis-ci.org/WP-API/wp-api-meta-endpoints.svg?branch=master)](https://travis-ci.org/WP-API/wp-api-meta-endpoints)
 
-## Description ##
+Just like other parts of WordPress, the REST API fully supports custom meta on posts, comments, terms and users. Similar to custom post types and taxonomies, only meta that opts-in to API support is available through the REST API.
 
-[![Build Status](https://travis-ci.org/WP-API/wp-api-meta-endpoints.svg?branch=master)](https://travis-ci.org/WP-API/wp-api-meta-endpoints)
+This plugin is a feature plugin for the main API plugin, and is expected to be integrated in the near future.
+
+
+## Meta registration
+
+For your meta fields to be exposed in the REST API, you need to register them. WordPress includes a `register_meta` function which is not usually required to get/set fields, but is required for API support.
+
+To register your field, simply call `register_meta` and set the `show_in_rest` flag to true.
+
+```php
+register_meta( 'post', 'field_name', array(
+	'show_in_rest' => true,
+));
+```
+
+Note: `register_meta` must be called separately for each meta key.
+
+
+### Meta Options
+
+`register_meta` is part of WordPress core, but isn't heavily used in most parts of core, so you may not have seen it before. Here are the options relevant to the REST API:
+
+* `show_in_rest` - Should the field be exposed in the API? `true` for default behaviour, or an array of options to override defaults (see below).
+* `description` - Human-readable description of what the field is for. The API exposes this in the schema.
+* `single` - Is this field singular? WordPress allows multiple values per key on a single object, but the API needs to know whether you use this functionality.
+* `sanitize_callback` - Callback to sanitize the value before it's stored in the database. [See the `"sanitize_{$object_type}_meta_{$meta_key}"` filter.](https://developer.wordpress.org/reference/hooks/sanitize_object_type_meta_meta_key/)
+* `auth_callback` - Callback to determine whether the user can **write** to the field. [See the `"auth_post_{$post_type}_meta_{$meta_key}"` filter.](https://developer.wordpress.org/reference/hooks/auth_post_post_type_meta_meta_key/)
+
+
+### API=Specific Options
+
+The `show_in_rest` parameter defaults to `false`, but can be set to `true` to enable API support. Out of the box, the API makes some assumptions about your meta field, but you can override these by setting `show_in_rest` to an options array instead:
+
+```php
+register_meta( 'post', 'field_name', array(
+	'show_in_rest' => array(
+		'name' => 'fieldname'
+	)
+));
+```
+
+The options you can set are:
+
+* `name` - The key exposed via the REST API. For example, if your meta key starts with an underscore, you may want to remove this for the API.
+* `schema` - The JSON Schema options for the field. Exposed via OPTIONS requests to the post. This is generated automatically based on other parameters, but can be specified manually if you'd like to override it.
+
+
+## Using Meta over the API
+
+Meta is added to existing resources as a new `meta` field. For example, to get the meta for a single post, fetch the post at `/wp/v2/posts/{id}`, then look in the `meta` field. This is a key-value map for the registered fields.
 
-WP REST API companion plugin for post meta endpoints.
+To update a field, simply send back a new value for it.
 
-## Changelog ##
+Setting a field to `null` will cause the value to be removed from the database. If a field has a default value set, this essentially "resets" the value to the default (although no default will be stored in the database).
 
-### 0.1.0 (February 9, 2016) ###
-* Initial release.
+For meta fields which can hold multiple values, this field will be a JSON list. Adding or removing items from the list will create or remove the corresponding values in the database.

codecoverage.xml

@@ -0,0 +1,30 @@
+<phpunit
+	bootstrap="tests/bootstrap.php"
+	backupGlobals="false"
+	colors="true"
+	convertErrorsToExceptions="true"
+	convertNoticesToExceptions="true"
+	convertWarningsToExceptions="true"
+	>
+	<php>
+		<const name="WPAPI_CODE_COVERAGE" value="1" />
+	</php>
+	<testsuites>
+		<!-- Default test suite to run all tests -->
+		<testsuite>
+			<directory prefix="test-" suffix=".php">tests</directory>
+		</testsuite>
+	</testsuites>
+	<filter>
+		<blacklist>
+			<directory suffix=".php">.</directory>
+		</blacklist>
+		<whitelist>
+			<directory suffix=".php">./lib</directory>
+			<file>./plugin.php</file>
+		</whitelist>
+	</filter>
+	<logging>
+		<log type="coverage-clover" target="build/logs/clover.xml"/>
+	</logging>
+</phpunit>

lib/class-wp-rest-comment-meta-fields.php

@@ -0,0 +1,21 @@
+<?php
+
+class WP_REST_Comment_Meta_Fields extends WP_REST_Meta_Fields {
+	/**
+	 * Get the object type for meta.
+	 *
+	 * @return string
+	 */
+	protected function get_meta_type() {
+		return 'comment';
+	}
+
+	/**
+	 * Get the type for `register_rest_field`.
+	 *
+	 * @return string
+	 */
+	public function get_rest_field_type() {
+		return 'comment';
+	}
+}