Skip to content

Conversation

@kadamwhite
Copy link
Collaborator

This release makes some key changes, adds some essential functionality, and re-wires things under the hood. I am unilaterally adopting the model of naming releases after albums, because I am releasing this in Vienna and "Mozart's House" by Clean Bandit (New Eyes, track 1) has been stuck in my head throughout WordCamp Europe.

Autodiscovery

Autodiscovery is now supported via the WP.discover method (#181)

Bootstrapping

If you already have the API response object you want to bootstrap with, the .routes property from it can now be passed in when calling WP.site or instantiating a new WP object (also #181, documented #182):

var site = WP.site( 'http://my-endpoint.com/wp-json', endpointJSON.routes );

A script to ease the process of downloading this JSON object was added in PR #175

registerRoute

Arbitrary methods for custom endpoints can now be added without auto-discovery by using the .registerRoute method, which takes the same route configuration strings as register_rest_route in the API core.

Internal Re-Architecture

In #168 the innards of the library were totally gutted and re-written to support autodiscovery, registerRoute and bootstrapping.

Human-Readable names for HTTP verbs

PUT and POST are not the most intuitive words for what they do, and POST in particular caused a lot of semantic confusion with the post object within the WordPress data model. .post has become .create, and .put has become .update.

Upgraded Dependencies

Package dependencies and developer tools have all been updated to the latest version in their respective ranges.

Props

@props to the community that submitted code, bugs, issues, questions, or comments that added to & informed this release. I am a believer in celebrating contributions beyond code commits because this project would not be going anywhere were it not for the people using (or attempting to use) this package.

For general advice & conceptual validation:

@rmccue

For assisting with the discussion about how to handle autodiscovery
and custom route endpoints:

@adamsilverstein
@aedensixty
@andreipot
@artoliukkonen
@BenHen75
@chrishutchinson
@elyobo
@gnarf
@ishaan-puniani
@jasonphillips
@joehoyle
@jupitercow
@timmyc

For opening issues and asking questions:

@aedensixty
@dasheck0
@JSteranko
@nabeards
@satish9323
@stompweb

We still owe responses to, and have not forgotten the questions of:

@MurhafSousli
@smedegaard
@tommedema
@vtripolitakis

This release makes some key changes, adds some essential functionality,
and re-wires things under the hood. I am unilaterally adopting the
model of naming releases after albums, because I am releasing this in
Vienna and "Mozart's House" by Clean Bandit (New Eyes, track 1) has
been stuck in my head throughout WordCamp Europe.

**Autodiscovery**

Autodiscovery is now supported via the `WP.discover` method (#181)

**Bootstrapping**

If you already have the API response object you want to bootstrap with,
the `.routes` property from it can now be passed in when calling `WP.site`
or instantiating a `new WP` object (also #181, documented #182):

```js
var site = WP.site( 'http://my-endpoint.com/wp-json', endpointJSON.routes );
```

A script to ease the process of downloading this JSON object was added
in PR #175

**registerRoute**

Arbitrary methods for custom endpoints can now be added without auto-
discovery by using the `.registerRoute` method, which takes the same
route configuration strings as `register_rest_route` in the API core.

**Internal Re-Architecture**

In #168 the innards of the library were totally gutted and re-written to support
autodiscovery, registerRoute and bootstrapping.

**Human-Readable names for HTTP verbs**

`PUT` and `POST` are not the most intuitive words for what they do, and
POST in particular caused a lot of semantic confusion with the post object
within the WordPress data model. `.post` has become `.create`, and `.put`
has become `.update`.

**Upgraded Dependencies**

Package dependencies and developer tools have all been updated to the
latest version in their respective ranges.

**Props**

@props to the community that submitted code, bugs, issues, questions, or
comments that added to & informed this release.

For general advice & conceptual validation:
@rmccue

For assisting with the discussion about how to handle autodiscovery
and custom route endpoints:
@adamsilverstein
@aedensixty
@andreipot
@artoliukkonen
@BenHen75
@chrishutchinson
@elyobo
@gnarf
@ishaan-puniani
@jasonphillips
@joehoyle
@jupitercow
@timmyc

For opening issues and asking questions:
@aedensixty
@dasheck0
@JSteranko
@nabeards
@satish9323
@stompweb

We still owe responses to:
@MurhafSousli
@smedegaard
@tommedema
@vtripolitakis
@kadamwhite
Copy link
Collaborator Author

No code in this patch but retroactive commentary on the new APIs from #181, #176, and #180 are always welcome

@kadamwhite kadamwhite merged commit 042fa89 into master Jun 25, 2016
@kadamwhite kadamwhite deleted the release-0.8.0 branch June 25, 2016 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants