This is easily fixable but I'm wondering if what exactly we should add tests want to the TCK as they are obviously missing do here .
The fact is that HV doc has the following sentence:
{quote}
`hasConstraints()` allows for a quick check whether an element has any direct constraints (e.g. class-
level constraints in case of `BeanDescriptor`).
{quote}
So I'm not sure wondering if we state explicitly somewhere that they should be taken take into account but the container element constraints at all in {{hasConstraints()}}. Moreover the {{ContainerElementTypeDescriptor}} also contains the cascading information and I think it ' s m not sure we want to take the reasonable thing cascading case into account in {{hasConstraints()}} as its definition seems to do be a bit more restrictive than what we have in the HV specific classes .
One other interesting point is that the {{ConstraintFinder}} present on an element does not take into account the container element constraints. |
|
