79bbfd19c9
The REST API does not provide a mechanism to distinguish between endpoints representing models and those representing collections, so the Backbone client must make that distinction internally. Previously wp-api.js accounted for `/users/me`, but not for `/settings`. This patch updates the logic so that `/settings` is properly registered as a Backbone model. When calling `wp.api.init`, additional endpoints can be specified to be models using the `modelEndpoints` argument. Props @adamsilverstein. Fixes #41056. git-svn-id: https://develop.svn.wordpress.org/trunk@41112 602fd350-edb4-49c9-b593-d223f7449a82 |
||
---|---|---|
.. | ||
customize-header.js | ||
customize-menus.js | ||
customize-settings.js | ||
customize-widgets.js | ||
js-widgets-endpoint.js | ||
updates.js | ||
wp-api-generated.js | ||
wp-api.js |