[bv-dev] Value extraction open issue #2: per constraint ConstraintsApplyTo?

[Gunnar Morling]

As a variation of Matt's idea, an optional index() parameter could be added:

    @Size(1)
    @Size(3)
    @ApplyConstraintTo(constraint=Size.class, index=1, target=WRAPPED_VALUE)
    List<String> nicknames;

It could be omitted (via a default value of -1 or similar) if there is
only one constraint of the type in question:

    @NotNull
    @Email
    @ApplyConstraintTo(constraint=NotNull.class, target=ANNOTATED_ELEMENT)
    Optional<String> email;

Does the trick, though it's still a tad verbose.


2017-01-13 14:58 GMT+01:00 Emmanuel Bernard <emmanuel at hibernate.org>:
>
> On 13 Jan 2017, at 13:29, Guillaume Smet <guillaume.smet at gmail.com> wrote:
>
> On Fri, Jan 13, 2017 at 1:01 PM, Gunnar Morling <gunnar at hibernate.org>
> wrote:
>>
>> Unfortunately, validationAppliesTo() is already taken:
>>
>> http://beanvalidation.org/latest-draft/spec/#constraintsdefinitionimplementation-constraintdefinition-validationappliesto
>>
>> It's used to distinguish between return value and cross-parameter
>> constraints.
>>
>> Any other name I can think of right now would make up for much
>> confusion with that option.
>
>
> Too good to be true :).
>
> That being said, I'm wondering if we could reuse it and just add 2 other
> values to ConstraintTarget. All in all, it's the same concept. The default
> being IMPLICIT is not too bad either.
>
>
> Right I think it’s worth exploring.
> I still like my group repurposing trick though even if it offenses the clean
> camp :)
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev