Adding custom schema format for comma separated emails #138
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.
Summary
Adding a custom format to the config validator that checks if a string has the format of emails separated by commas, for example:
[email protected],[email protected]. This new format is used to validate thenotificationInfo.tofield in the configNew behavior
The config validator will now ensure that the
notificationInfo.tofield of the config is either an array of emails or a string of emails separated by commasCode changes
comma-separated-emails, added toconfigValidator.jswhich splits a string at any commas, strips excess whitespace and then validates the resulting strings against Ajv's email format regexconfig.schema.jsonupdated to usecomma-separated-emailsfornotificationInfo.toTesting guidance
Here are some variations to test:
[email protected]a single email should still be validtest#example.coma single invalid email should not be valid[email protected],[email protected]emails separated by comma should be valid[email protected],demo&example.comshould not be valid if any item is not a valid email