cbValidation
v1.x
v1.x
  • Introduction
  • Overview
    • Installation
    • Configuration
    • Declaring Constraints
      • Configuration File
      • Domain Object
      • A-la-carte
    • Available Constraints
      • Unique Constraints
      • Constraint Custom Messages
      • Custom Message Replacements
    • Validating Constraints
      • Validating With Failures
      • Validating with shared constraints
      • Validating with a-la-carte constraints
      • Validating Custom Fields
    • Displaying Errors
    • WireBox DSL & Integration
  • Advanced
    • i18n Integration
    • Advanced Custom Validators
    • Custom Validators
    • Custom Validation Managers
Powered by GitBook
On this page

Was this helpful?

Edit on Git
Export as PDF
  1. Overview

Declaring Constraints

PreviousConfigurationNextConfiguration File

Last updated 5 years ago

Was this helpful?

You can define constraints in several locations:

When validating using validate(), validateOrFail() you have to specify a target, but specifying a constraint in your call is optional.

Constraints Discovery

When you call the validation methods with NO constraints passed explicitly, then the validation module will following this lookup procedure:

  • Lookup your constraints in myTarget.constraints struct in your target object or struct.

  • If you specify your constraint parameter as a string, the validator will lookup a shared constraint in your configuration file.

  • If you specify your constraint parameter as a struct, this struct will directly server as your set of constraints, so you can specify your constraints on the fly, or specify an alternative set of constraints in your model, e.g User.constraints vs User.signInConstraints

Configuration file
Inside domain object
A-la-carte