Convert AJAX endpoints to REST API routes

[MichelleBlanchette]

There seems to be no way to retrieve an object's title by just having the ID, like you can in PHP with the generic get_post( $id ) call. With the REST API v2, you must already know the post_type of the object, which is obviously no good when you only have the object ID. So we gotta make our own endpoint!

And since I want to convert all AJAX endpoints to REST routes, anyways, you might as well go ahead and make our Rest_Routes class so we can easily migrate everything in a future release. 🚀 Be sure to segment Asana routes from generic, WordPress routes such as this.

I discovered this bug by saving a Page object ID to the automations Pin Post field which uses the /wp/v2/posts/{id} endpoint to load the title label for the initial value. Turns out this endpoint is for literally posts... And with custom post types, this just becomes a disaster—especially because custom post types do not automatically have routes set because some are private (only used internally/programmatically), so keep this in mind when displaying search results!!! It can easily get super messy! And then just add a filter if people want to allow private/hidden post types in search results. 👍

[MichelleBlanchette]

Just went with an AJAX endpoint for now to get release out faster in commit 0fe5c60

[MichelleBlanchette]

The AJAX endpoint works great, so there's no need to change it. Let's definitely get all AJAX usage switched over to REST API endpoints, though. They are more efficient and accessible. 👍