This post summarizes the weekly REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. chat meeting for June 27, 2019. (Slack transcript). Weekly REST API component office hours are held every Thursday at 18:00 UTC in the #core-restapi room in the Make WordPress Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Ticket Created for both bug reports and feature development on the bug tracker. Review
#43691 is close to being ready for commit. @timothybjacobs raised the question of how strict WordPress should be about enforcing the use of the 204 status code. @kadamwhite agreed that core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. shouldn’t be that stringent.
#43392 has received some more feedback. @timothybjacobs is working on a refreshed patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. @spacedmonkey wanted to know how the ticket would impact #43941. @kadamwhite didn’t think they’d conflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. and whichever ticket landed first would require the other to be adjusted.
#47443 came up in a recent REST API bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub. It touches post type capabilities which can be tricky. Feedback from developers with post type capabilities experience would be very helpful.
Menus Endpoint
@spacedmonkey has continued work on the Menus Endpoint. A discussion ensued about how to get better feedback on open PRs. Johnny is planning on writing up some basic test instructions. Subsequent PRs will hopefully be smaller and easier to test in the future.
The Menus Location endpoint was discussed. In particular, what endpoint should be responsible for assigning a menu to a menu location. @spacedmonkey‘s gut reaction is that menu-locations are like categories. You assign a category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. on the post endpoint, so a menu location should assigned on the menu. @kadamwhite and @timothybjacobs had similar initial thoughts.
@kadamwhite brought up that it’s a bit of a flip from the existing UI User interface model, where you start with a location and then add a menu to it.
@timothybjacobs suggested modeling it after the existing posts controller, at least for the first iteration.
Upcoming Meetings
#rest-api
