value
any
fieldProps
Object
fields
Object
form
Object
extra
Object
missing
invalid
async
name
type
general
{ ruleName: message }
map as the value of the rule
key in the respective selector:Note: Named resolver must have the corresponding validation rule with the same name in order to resolve. Otherwise, the closest validation message will be returned by the resolver. Considering the example above, ifminLength
rule doesn't exist and thetype=["password"]
field is invalid, the closestinvalid
resolver will be used (which istype.password.invalid
in this case).
messages.name[fieldName][ruleName]
messages.name[fieldName].invalid
/ messages.name[fieldName].missing
messages.type[fieldType][ruleName]
messages.type[fieldType]invalid
/ messages.type[fieldType].missing
messages.general.invalid
/ messages.general.missing
includesAt
validation rule would reject, marking the field as unexpected. This must be reflected in the UI using the validation messages schema.name.userEmail.rule.includesAt
name.userEmail.invalid
type.email.invalid
general.invalid