Admin Page: Make settings updates have better notice messages#10972
Admin Page: Make settings updates have better notice messages#10972
Conversation
|
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: January 10, 2019. |
| export const updateSettings = ( newOptionValues, type = '' ) => { | ||
| export const updateSettings = ( newOptionValues, noticeMessages = {} ) => { | ||
| return ( dispatch ) => { | ||
| let messages = { |
There was a problem hiding this comment.
Comment for the reviewer. Basically this block was moved into mapUpdateSettingsResponseFromApi and the messages have been delegated to the component dispatching the action to one of the actions creators mapped into its props.
| if ( false === ! newPhotonStatus && 'active' !== photonStatus ) { | ||
| newPhotonStatus = false; | ||
|
|
||
| this.props.updateOptions( { |
There was a problem hiding this comment.
Comment for the reviewer: There were two calls to this.props.updateOptions() being done here. Now, let's collect the settings, and only then call the action creator once.
|
You can see in the gif, that the only customization provided by this PR is the site accelerator notice for when updating the general toggle. |
keoshi
left a comment
There was a problem hiding this comment.
Other than the note I've added about capitalization this works great in my testing!
jeherve
left a comment
There was a problem hiding this comment.
This works well for me, and gives us the opportunity to change more and more settings in the future with updateOptions. 👍
|
Thanks Osk. the functionality works great. |
* Add first version of the Changelog and testing list for 6.9 * Changelog: add #10710 * changelog: add #10538 * changelog: add #10741 * changelog: add #10749 * changelog: add #10664 * changelog: add #10224 * changelog: add #10788 * Changelog: add #10560 * Chanegelog: add #10812 * changelog: add #10556 * Changelog: add #10668 * Changelog: add #10846 * Changelog: add #10947 * Changelog: add #10962 * Changelog: add #10956 * Changelog: add #10940 * Changelog: add #10934 * Changelog: add #10912 * changelog: add #10866 * changelog: add #10924 * Changelog: add #10936 * Changelog: add #10833 * changelog: add #10867 * Changelog: add #10960 * Changelog: add #10888 * changelog: add #10840 * changelog: add #10972 * Changelog: add #10979 * changelog: add #10909 * Changelog: add #10958 * Changelog: add #10981 * Changelog: add #10564 * Changelog: add #10809 * Changelog: add #10982 * Changelog: add #10706 * Changelog: add #10978 * Changelog: add #10132 * Changelog: add #11022 * Changelog: add #11024 * Changelog: add #10875 * Changelog: add #11030 * Changelog: add #11053 * Changelog: add #10880 * Changelog: add #9359 * Changelog: add #11037 * Update block list * Changelog: add #11060 * Changelog: add #10755 * changelog: add #11000 * Changelog: add #10786 * Changelog: add #10945 * Changelog: add #10597
Addresses #10640 partially. The scope of the messaging updates needs the structure introduced in this PR but has a wider reach than just the accelerator message.
Changes proposed in this Pull Request:
updateSettingsto handle the custom message in a tidier way. With a api response mapping function. 7464fadmessagesparameter with an object holding the notice messages as strings. Refactors the High Order componentconnect-module-optionsto better handle theregeneratePostByEmailAddress()request and also to accept themessagesparameter for theupdateOptionsmethod. 4a19c58Testing instructions
for designers
Testing instructions for developers
As this PR refactors stuff affecting other settings please check the above, but also
Proposed changelog entry for your changes:
Screeshots