- All Known Subinterfaces:
- FieldConstraintDocChecker, FieldConstraintValueChecker
- All Known Implementing Classes:
- ArraySizeChecker, EmptyFieldConstraintDocChecker, EnumChecker, IdentityChecker, MatchesChecker, MinMaxChecker, RequiredChecker, StringLengthChecker
public interface FieldConstraintChecker
Base interface for field constraint checkers. There are two flavors of
constraint checkers: FieldConstraintDocChecker is called with the document to
allow for constraints validation even if the field does not exist in the
document. FieldConstraintValueChecker is called with the value of every
field, so these are not called for nonexistant fields.
Rationale: Constraint validator iterates through the values that match a
certain path. If a value does not exist, the iterator doesn't go through it.
So, those need to be caught using the FieldConstraintDocChecker. For simple
fields, the logic to figure out that an expected field does not exist is
trivial, but things get hairy for objects that are array members, and there
are missing fields there.
- See Also:
FieldConstraintDocChecker,
FieldConstraintValueChecker