Make validators and sanitizers run in the order they are specified#722
Merged
gustavohenke merged 37 commits intomasterfrom Jun 14, 2019
Merged
Make validators and sanitizers run in the order they are specified#722gustavohenke merged 37 commits intomasterfrom
gustavohenke merged 37 commits intomasterfrom
Conversation
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This a breaking change from previous versions.
Take this sample validation chain:
How it used to be:
escaperuns first, thenisEmail, then the custom validator. Sanitizers would always run first (in the order they are specified among them), then validators (in the order they are specified among them).How it will be from now on:
isEmailruns first, thenescape, then the custom validator. The validators or sanitizers will run in the order they are specified.This architecture is now called "context stack", which allows us to better implement things like #500 or maybe even #658.