feat: add support for optional custom error messages by using ajv-errors#44
Merged
Conversation
dsanders11
changed the title
dsanders11
approved these changes
Jul 4, 2025
dsanders11
left a comment
dsanders11
left a comment
Owner
There was a problem hiding this comment.
This is a great PR, thank you! 😀
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Some features of JSON schema validation such as
if-then-elseandnotprovide error messages that are quite difficult to understand without checking the schema definition.ajv-errorsprovides an easy way to workaround that by providing a keyworderrorMessagewhich greatly extend how you can describe validation errors.In this PR I added optional support for the use of
ajv-errorsby using the input flagcustom-errorsin the input.