JavaScript support via REST API

[JasonTheAdams]

The requirements doc mentions a REST API to support the client from JS. The challenge here is that this repo is intended to be a client library, not an HTTP server, so we probably want to avoid handling the REST endpoints from this repo.

Another idea that was proposed was adding a REST specification to this repository. The specification would outline the endpoints that an implementing systems should have to provide a RESTful interface for the client. This specification could then be used to create the endpoints in the WP REST API — in a separate project which has the integration.

[felixarntz]

This is what I initially had in mind, and I still think it would be very valuable. That said, I think we could start with a WordPress-centric approach for the REST API and JavaScript implementation, purely for pragmatic reasons. As a long-term solution I very much prefer a specification that different platforms could implement, and then a JS package could be implemented that's platform agnostic too.

I'm definitely open to doing it that way from the beginning too, just want to be mindful of potential overhead of doing everything in a platform-agnostic way from the start. Let's continue discussing the trade-offs, and with time we'll probably get a better idea of how much initial overhead an agnostic specification approach would have over a more pragmatic straight-to-WordPress approach.

[JasonTheAdams]

Agreed! I think it makes sense to circle back on something like a specification within this repository after we've already built it within the WP REST API — giving us the benefit of experience. No need to try and start with a specification or anything in this repo until then, I think.

[Jameswlepage]

No need to try and start with a specification or anything in this repo until then, I think.

+1 - I do envision the specification helping define the way the WordPress-centric approach works, but I think it's okay if it grows from the maturing WordPress implementation itself.