I miss 2 options that would make AttributeValidator much more powerful:
contain the substring (where the substring could be a regexp) rule,
checkbox to negate rule
But would be great to have the flexibility and options as in TestFilter.
By the way, is it a good idea to put AttributeValidator and TestFilter together, and use a checkbox for selecting to create ports for each rejection or reject at the end with a list of the unmatched rules?
Just the ability to choose whether empties/missing/null can be passed alongside an additional test would be useful, even if more complicated conditional tests weren't possible.
I've built a BulkAttributeValidatorWithMapping, takes external configuration file like SchemaMapper, allows logical testing like Tester (including NOT), can group tests together (composite tests - eg "Attribute A is a number, or Attribute A is blank"; or... "Attribute A is ABC or Attribute B is DEF"), and custom error messages can be entered (each failed test is concatenated onto an error string). It works with un-exposed attributes (designed to work with an upstream SchemaMapper). May take a while to run as it checks each feature against each validation rule.
Â
If anyone is still following this thread and is interested, I'd appreciate any feedback.