[wp-trac] [WordPress Trac] #30937: Add Customizer state persistence in changesets (formerly “transactions”)

[WordPress Trac]

#30937: Add Customizer state persistence in changesets (formerly “transactions”)
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
     Type:  feature request                      |  westonruter
 Priority:  high                                 |      Status:  closed
Component:  Customize                            |   Milestone:  4.7
 Severity:  normal                               |     Version:
 Keywords:  has-patch needs-testing needs-unit-  |  Resolution:  fixed
  tests                                          |     Focuses:
-------------------------------------------------+-------------------------

Comment (by nikeo):

 Replying to [comment:82 westonruter]:

 OK thanks got it. The solution in my case will be to override the
 `api.previewer.query` method only in a refresh case, to always post the
 full set of customized values (and not only the ones not yet saved in the
 DB changeset)
 The new utility `api.dirtyValues()` with `{ unsaved : false }` as param
 will be my friend.

 > Feel free to ping me on #core-customize in Slack to chat about this
 further as it's probably a better place to discuss your use case.
 I will for my next message about this.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30937#comment:83>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform