Support Dictionary for Error Messages #10
Merged
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
bajb
approved these changes
Aug 8, 2025
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.
Now supports a Dictionary (if passed through).
The validator will serialise with a new field
'd'e.g.{'d': {'invalid': 'Required'}}this will then be used as the error message in JS.The reason for this is so we can create, for example
RequiredValidator::withDictionary([RequiredValidation::DICT_INV -> "Translated Error Message"])in PHP and also have the translated message in JS.If you don't overwrite all the keys, that's fine it array merges so it has fallback.
Can still be used standalone as the JS fallbacks to the original if there is no Dictionary.
Can still be used as before simply calling
new RequiredValidator()