BREAKING:fix: validate should use all set by default if no specific validator exists #67
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 validators is an array, always run regardless of specified set (because using an array is a shorthand for
{ all: [...] })If validators is an object, use the specified set validator, if it doesn't exist, fall back and use the
allvalidator.Use case:
In schemata's current state, if you validate
{}with thetestset, it will only fail validation onagencyfield.With these changes, it will correctly fail on all fields.
If you need to disable a validator field, you simply:
Or just omit
validators