Apply server-sanitized settings to JS client on saved #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
westonruter
force-pushed
the
feature/apply-server-sanitized-settings-to-js-client-on-save
branch
from
324cb10 to
6209a5c
Compare
westonruter
force-pushed
the
feature/apply-server-sanitized-settings-to-js-client-on-save
branch
from
6209a5c to
beb67ec
Compare
westonruter
force-pushed
the
feature/apply-server-sanitized-settings-to-js-client-on-save
branch
from
beb67ec to
79c7d6e
Compare
westonruter
added a commit
that referenced
this pull request
Dec 17, 2015
…s-to-js-client-on-save Apply server-sanitized settings to JS client on saved
westonruter
deleted the
feature/apply-server-sanitized-settings-to-js-client-on-save
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If server-side sanitization modifies a value when saving, make sure that this modified value gets applied to the JS client and results in a non-dirty state.
(Note there a possibility of a race condition for widgets since they currently rely on a separate
update-widgetAjax request to sanitize their values.)