WP REST API Content Endpoints Conditionally Approved for Merge in 4.7


The WP REST API team and WordPress core contributors met tonight to decide whether to merge the content endpoints in 4.7. After the merge proposal was published a week ago, several core developers expressed concern regarding the brokered authentication scheme and the team has since decided to remove it from the proposal in favor of focusing on it for the 4.8 development cycle.

Discussion at the meeting tonight centered around six topics: security, performance, user feedback, if merging will negatively impact API development, whether content endpoints will benefit core development, and whether those endpoints belong on every WordPress site. The team also discussed possible ways to measure the success of the project once it has been merged into core.

Contributors agreed on a conditional approval for merging the endpoints, provided that the team address outstanding questions on object meta and that others outside of the REST API team provide a proof of concept for how WordPress core can use the endpoints. These conditions must be met before the enhancement deadline next Wednesday.

“Making something work in core does not mean committing it to trunk,” WordPress 4.7 release lead Helen Hou-Sandí said. “This is also a call to the greater dev community – there is a chance to do something that doesn’t necessarily carry the weight of being shipped in core that can serve as proof that you want something. A developer’s vote.”

Hou-Sandí said that requiring the proofs to be created by developers outside of the REST API team will demonstrate “how other people experience the development process.” It also frees up the project’s team to focus on other pre-merge tasks.

Multiple proofs of concept are encouraged and some of the features being considered include Press This, Quick Draft, infinite scroll on admin list tables, and anything else anyone wants to try. Adam Silverstein volunteered to take a crack at Press This and by the conclusion of the meeting said, “I’ve got Press This creating new posts already actually, that was pretty straightforward to switch over.” He plans to include his work in a new ticket on trac.

“I have no blocking objection but I am pretty wary and want to make sure that conditions for keeping in 4.7 are hammered out in the next 24 hours and conditions for beyond worked on before beta,” Hou-Sandí said. Matt Mullenweg, who has been one of the most vocal critics of the project’s readiness so far, agreed with her statement but also said he isn’t yet satisfied with how the team plans to measure the success of the project.

“I also feel like the measure of success is still woefully undefined, and there’s still a lot of fuzziness in the core arguments of ‘if this is in [core] people will use it more,’” Mullenweg said.

Contributors seem very motivated in the final stretch and are working towards producing the necessary proofs of concept prior to the enhancements deadline. If any of the proofs are solid enough to be merged, the WP REST API content endpoints will ship in WordPress 4.7 alongside a core feature that is using the API.


6 responses to “WP REST API Content Endpoints Conditionally Approved for Merge in 4.7”

  1. It was a delightful meeting to attend and watch wonderful arguments/conversations. Glad the REST-API finally getting in WordPress core for a many of us to enjoy and work with the awesomeness in the future.

    A zillion thanks to the team and everyone who worked on to get it this far.

  2. I would really like to participate in this development but I’m not sure where to start. If I’d like to submit a proof of concept, where do I submit it? Also, what are the parameters for the proof (is there anything a proof shouldn’t do or use?). This is a potentially great addition to WP and I’d really like to see it either be part of the core or, at the very least, a plugin that ships with WP by default (possibly better that way).


    Ted Stresen-Reuter

  3. I find the REST API to be both interesting but also empty. It’s needed in core but there isn’t as much adoption as I would have thought. The REST API is being used primarily in “proof of concept plugins” and there are very few that I know of that make full and proper use of the API currently. This might just be because of how only the first half was in core but it is interesting that we don’t see more adoption of it.

    In no way am I saying it should not be included or to be removed it’s just a little odd that there is a lot more buzz to get it in core than for those to actually build off of it no?

    • I think it’s one of those “If you build it they will come” scenarios. The plugin suffered from a change in endpoints/schema. The first half of core suffered from “Oh well not even WordPress is using it”. That being said we have done a lot with the REST API and there’s a movement behind some of the stuff that’s going to end up in core to use it for various parts of WP’s interface. No refreshing to delete posts or save menus… or update posts. Development may seem slow moving, but the hype will come.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: