Whenever you go to the Wordcamp to spend time with developers, it’s hard to notice your interest in the new WordPress rest API. The rest API team launched plug-in version 1.2 and continued to develop it with the goal of merging it into the core of word press. This is a larger project than Ryan McCue, who led the project with Rachel Baker. I recently discussed with Ryan the challenges of these huge projects, as well as the complexity of generating a \
Version 1.2 and compatibility with earlier versions of the plug-in version 1.2 are the last planned major releases of the rest API as a plug-in. The team is now focused on version 2. Since the launch of version 1, Ryan has been fully supporting version 1 and ensuring compatibility with previous versions. This is what he and the rest API team are still committed to. Version 2 of the code that will be incorporated into the WordPress core is completely incompatible with version 1, but the plug-in will continue to act as a compatibility layer with older versions. In this way, as long as the rest API is in the kernel and all plug-ins developed with plug-in versions are active, they can work. The
Ryan said in an interview, \
\
By default, the rest api code base is divided into two parts. The first is the infrastructure for creating restful APIs. The other part is the default endpoint provided. Infrastructure can go into the core before adding endpoints. In this case, the infrastructure was initially marked as an experimental API. This mimics the way the heartbeat API slowly introduces the core between two or more versions. Generic API I asked Ryan about creating a \
He looked at the two main core use cases for the API. The requirements of both are conflicting. The first use case is what he calls a \
