Replace validation Group by a validation context

My project should be available for many country and validation rules can be different for each contry.

For exemple:

public class User {
    public String firstName;
    public String lastName;


    private static final ValidatorBuilder<User> VALIDATOR = ValidatorBuilder.<User>of()
            .constraint(User::getFirstName, "firstName", Constraint::notNull)
            . constraintOnCondition((user, group) -> isItalian(), b.constraint(User::LastName, "lastName", Constraint::notNull))
}

In this example the lastName is mandatory only for Italian. Actually using yavi I can not implement the isItalian function since I need to read an HTTP header to know if it’s italian or not.

so I think that have a context instead of a group can be fine to solve this issue. We can do something like that:

. constraintOnCondition((user, context) -> context.get("countryCode").equals("IT"), b.constraint(User::LastName, "lastName", Constraint::notNull))

Another solution it to create a group by country, but i can can hard to maintain. If I already use a group EDIT CREATE, I will have EDIT_FR, CREATE_FR, EDIT_IT, CREATE_IT, I think that It can be hard to manage.

[making]

@deblockt I just sent a pr (#216) to introduce ConstraintContext. I’ve tried backwards compatibility, but it may break the code of advanced users like @duponter . I would appreciate your feedbacks.

[duponter]

Our code with the ConstraintGroups is still experimental. This is a welcome addition to the library. Therefore, we will update our code to use the context instead of the groups.