Daniel Bachhuber
Daniel Bachhuber
Before the Posts controller lands in core, we need to come to some reasonably clear decision on to what degree the REST API supports custom post statuses. For the gory...
To better ensure we don't make a typo that breaks a `_link`, we should programmatically test to ensure all `href` resolve to a valid URL.
We should have a more structured way of testing that only present fields are updated. Having to write test cases like #911 each time will get painful. Related #864
Let's make sure our controllers have a consistent pattern of filters and actions.
It would be nice to have a supplemental plugin for API key authentication. API keys would be tied to specific user accounts. A request authenticated by an API key would...
Currently we include all supplied arguments. However, this poses the opportunity for data to leak through without sanitization. We should be extra safe and only include registered arguments.
Eve has a [useful solution for concurrency control](http://python-eve.org/features.html#data-integrity-and-concurrency-control): ETags: > API responses include a `ETag` header which also allows for proper concurrency control. An `ETag` is a hash value representing...
Given we're conditionally using admin utilities that WordPress doesn't load by default, we should be running the test suite without loading admin utilities by default. Might be time to switch...
Core has presentational functions like `post_class()` which are dynamic basic on context. They're also not really "resources" that you'd expect to be able to manipulate through WP-API. - What are...
Related to #1, we should have some over-arching best practice documentation for users to register their own endpoints.