Make WordPress Core

Changes between Version 1 and Version 4 of Ticket #39634


Ignore:
Timestamp:
02/14/2017 08:25:10 PM (8 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39634

    • Property Keywords needs-patch added
    • Property Version changed from to 4.7
  • Ticket #39634 – Description

    v1 v4  
    11In order to make the customizer a REST API-backed application, the objects that it uses need to have REST API endpoints. In addition to having an endpoint for changesets (#38900), there should be endpoints for getting a list of the panels, sections, controls, settings, and partials. One immediate benefit for these endpoints will be to allow for the objects to be lazy-loaded when needed (#28580) to improve performance. Having schemas attached to `WP_Customize_Setting` would also allow controls to be generated automatically with the appropriate validation constraints (#38845). This will also facilitate bootstrapping the customizer onto the frontend so that customization can be done without going to `customize.php`.
     2
     3Feature plugin repo: https://github.com/WP-API/wp-api-customize-endpoints