For the login field, only letters and numbers will be accepted, the email should be valid, and born should be a valid date.
Therefore validation will fail if the field is not present in the dataset, but may (depending on the rule) succeed if the value submitted is empty (‘’).
The ‘on’ key can be set to either one of the following values: ‘update’ or ‘create’.
The specified ‘rule’ may be the name of a method in your model, a method of the core Validation class, or a regular expression.
For more information on the rules available by default, see will make the field required only for update or create operations.
Now that you’ve seen the big picture on how validation works, let’s look at how these rules are defined in the model.
There are three different ways that you can define validation rules: simple arrays, single rule per field, and multiple rules per field.
This fiddle shows an input field with a valid date value being validated using a regex.
The regex itself works as demonstrated, and matches what it should, yet the form validation still returns false. This regexp : reg Exp[/^ [0-9]$/] Don't validate 41791234567 I have that message in web console : Uncaught Syntax Error: Invalid regular expression: /^ [0-9]$/: Nothing to repeat I think that your unvalid form is not due to your regexp but to semantic-ui form regexp rule handler Hi I was trying to use Reg Exp /(19|20)\d\d//\s(0[1-9]|)[:][1-6]\d/ for getting a date and time format like 1998/04/04 , but it does not validate the same.
For more information about how to handle the displaying of validation errors, check out array is added to the User Model, but the array contains no validation rules.