Question: What's the recommended approach for nested object validations?

[ib-jamesp]

I have a reasonably complex object graph, and want to be able to split up the validation of these objects into smaller unit testable chunks, yet retain the nested property structure provided when you validate inline such as the example:

try {
    validate(employee) {
        validate(Employee::company).validate {
            validate(Company::city).validate {
                validate(City::name).isNotEmpty()
            }
        }
    }
} catch (ex: ConstraintViolationException) {
    ex.constraintViolations
        .map { "${it.property}: ${it.constraint.name}" }
        .forEach(::println)
}

Is it possible to have the company.city validation in another class, yet called inline?

try {
    validate(employee) {
         //something like...
            companyValidator.doValidation(employee.company)
        
        }
    }
} catch (ex: ConstraintViolationException) {
    ex.constraintViolations
        .map { "${it.property}: ${it.constraint.name}" }
        .forEach(::println)
}

[ib-jamesp]

I have sort of answered my own question, and it is possible... but is it something you recommend?

 validate(Employee::dependents).validateForEach {
                    dependentValidator.doValidation(it)
                }

[Areks]

Hi, I agree, each class should know how to validate himself and if it's validation haven't got any complex condition depending on sibling objects call it internal validation rules look like pretty good