feat(ajv): Keep original validation type while using errorMessage
#728
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.
When
errorMessage
is used, ajv returns a special error object,error.keyword='errorMessage'
, and keeps original validation errors in theerror.errors
field.The proposed changes normalize the ajv validation errors by unwrapping the
errorMessage
error object, so the resolver returns original error types, such as required and pattern, while using custom error messages. The normalization also allows us to useerrorMessage
at the root level (fixes #615).As you can see in the before and after outputs, the value of the
type
field and the keys of thetypes
field use the original validation type instead oferrorMessage
.Before
After
Example schema
Input Value
Resolver Output
Input Value
Resolver Output