Feature: Multiple validation rules for the same name/type

Branch: feature/validation-multiple-rules

What

Need to have a support for multiple validation rules for the dedicated name or type.

Why

This would grant a flexible validation procedure coupled with the respective validation messages.

How

Let the validation groups have the named validation rules. Those names will be then used in the validation messages to bind them to the respective message.

Validation rules:

{
  type: {
    password: {
      minLength: ({ value }) => (value.length > 7),
      capitalLetter: ({ value }) => ...
    }
  },
  name: {
    confirmPassword: {
      matches: ({ value, fields }) => (value === fields.password.value)
    }
  }
}

Validation messages:

{
  type: {
    password: {
      missing: 'Please provide the password.',
      invalid: 'General message for unexpected field; fallback for the named rules without the corresponding named message.',
      custom/specific/byRule: {
        minLength: 'Password must be at least 8 characters long.',
        capitalLetter: 'Include at least one capital letter.'
      }
    }
  },
  name: {
    confirmPassword: {
      matches: 'The passwords do not match.'
    }
  }
}

This should validate the <Field.Input type="password" name="confirmPassword" /> relatively to the password “type” and its messages, and to the “confirmPassword” name and its messages.

[Vidlec]

And I agree messages and rules should be in different files.

[kettanaito]

Changes implemented and are available since version 0.18.0. Published.

Closing.