In the beginning, validations on the models were originally created using an EmailFormat concern and a StringFormat concern with regexes and messages. Later, a custom validator, StringFormatValidator, was used that generates better error messages and is more developer-friendly.
However, there is still some usage of the older EmailFormat and StringFormat concerns.
Solution
Remove the EmailFormat and StringFormat and replace them with the new StringFormatValidator.
Also
Two tangentially related things have been added/changed:
The "at least one digit" requirement has been removed from password
An new :only_printable_characters requirement has been added to password
Problem
In the beginning, validations on the models were originally created using an
EmailFormat
concern and aStringFormat
concern with regexes and messages. Later, a custom validator,StringFormatValidator
, was used that generates better error messages and is more developer-friendly.However, there is still some usage of the older
EmailFormat
andStringFormat
concerns.Solution
Remove the
EmailFormat
andStringFormat
and replace them with the newStringFormatValidator
.Also
Two tangentially related things have been added/changed:
password
:only_printable_characters
requirement has been added topassword