Toshiaki Maki

@kazuki43zoo FYI

Thanks for the request. It makes sense to add that functionality.

@sergtitov Can you give me a more specific usage example? It's true that you can't use it like the above, but I'd like to consider if there is an alternative...

I'm considering expanding the use of `constraintOnCondition` to collection.

@sergtitov It seems that your case is already feasible using `constraintOnCondition`. Can you check the example? https://gist.github.com/making/facf1fce97c5d6686b017618c4959e15

@deblockt The validation logic should be in the customer class. ```java import am.ik.yavi.builder.ValidatorBuilder; import am.ik.yavi.core.Validator; public class Customer { public CustomerType type; public InvoiceInformation invoiceInformation; public boolean isCustomerTypePro() { return...

Thanks for the write up! > Do you want to stay on JDK 8? Yes. I will support Java 8 until YAVI 2.0. At the moment, there are few packages...

What are the use cases that require this constraint? Do you think the addition of this constraint will provide more value than the increased maintenance costs?

Hmmm, it doesn't seem like a valid use case to me. Leave this PR open until further requests come in.

@runeflobakk I think the behavior is as expected. Implementationally, failFast is determined by the flag of the parent Validator. How does the below work? ```java Validator aValidator = ValidatorBuilder.of(A.class) .nest(A::b,...