Wordpress/tests/qunit
Dominik Schilling (ocean90) a2c633fdc7 REST API: Allow setting post formats even if they are not supported by the theme.
A `post_format` not used by the current theme, but supported by core is not a wrong/broken piece of information. It's just not used at this point in time. Therefore we should allow setting and retrieving any of the standard post formats supported in core, even if the current theme doesn't use them.

After this commit, a post's `format` value can survive a round trip through the API, which is a good general design principle for an API.

Merge of [40120] and [40121] to the 4.7 branch.

Props JPry, iseulde, davidakennedy, Drivingralle.
Fixes #39232.

git-svn-id: https://develop.svn.wordpress.org/branches/4.7@40137 602fd350-edb4-49c9-b593-d223f7449a82
2017-02-27 20:02:43 +00:00
..
editor TiinyMCE: update to 4.4.3, changelog: https://www.tinymce.com/docs/changelog/#version443-september12016 2016-10-11 00:09:03 +00:00
fixtures REST API: Allow setting post formats even if they are not supported by the theme. 2017-02-27 20:02:43 +00:00
vendor
wp-admin/js Customize: Ensure that qunit test enters in expected state and tests `wp.customize.dirtyValues` in starter content context. 2016-10-28 03:28:07 +00:00
wp-includes/js REST API: JavaScript client - improve route discovery for custom namespaces. 2017-02-24 22:47:47 +00:00
.jshintrc
index.html REST API: JavaScript client - improve route discovery for custom namespaces. 2017-02-24 22:47:47 +00:00