Hi, > Christanto's types know about "multiple" and "required" attributes
Those are for AttributeDefinition. I don't think we need complex validation for Attribute. But for Property, pluggable validation is already supported by its API [1]. Cheers, Christanto [1] https://github.com/christanto/sling-whiteboard/blob/a2cf3643b0c94181200705b7a11c756dc8684bd3/modeling/org.apache.sling.types.api/src/main/java/org/apache/sling/types/data/Property.java#L92 On Thu, Jan 10, 2019 at 10:45 PM Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Thu, Jan 10, 2019 at 3:36 PM Carsten Ziegeler <cziege...@apache.org> > wrote: > > This seems to have a lot in common what we already tried with the > > validator api/module. > > > > https://github.com/apache/sling-org-apache-sling-validation-api ... > > Indeed, thanks for pointing this out. > > I was planning to merge ideas once we progress - for now I think > Christanto's types know about "multiple" and "required" attributes, we > probably need to add a more opaque Validator interface that might use > this existing module underneath. > > But that can happen once we have at least an embryo of the Types API > which I think should start as small as possible. > > -Bertrand >