judo-runtime:custom-validators

The JUDO framework supports custom validation by implementing the `Validator` interface and registering it with the `ValidatorProvider`. This enforces domain-specific business rules and complex data integrity constraints beyond standard validations.

Yes, the JUDO framework supports cross-field validation through the custom `Validator` interface. You can implement validation logic that checks relationships between multiple fields within a payload, such as ensuring an `endDate` is not before a `startDate` in a booking system.

Attribute-specific validation applies custom checks to specific data attributes based on their name, type, or other characteristics. Within the JUDO framework, you create validators targeting individual fields to enforce domain-specific business rules and data integrity constraints.

No, the JUDO custom validator requires no external dependencies. It operates entirely within the JUDO framework using a defined `Validator` interface and dynamic registration mechanisms via the `ValidatorProvider` to enforce business rules.

The best way to enforce specific data formats in JUDO is creating a custom validator. By implementing the `Validator` interface, you can define reusable validation logic to ensure attributes like emails follow exact company formatting requirements.

Use custom validators when standard validations cannot enforce complex domain-specific business rules. You need them for cross-field constraints or attribute-specific logic, like verifying date ranges or applying custom formatting rules within the JUDO framework.