adding allOf validation and test cases #438
Conversation
|
First of all, thank you for the proposal. Instead of test cases being a,b,c,x,y,z blah blah, please use use cases that explain why you need this feature. See also #191 |
| @@ -42,6 +42,7 @@ enum Default implements ViolationMessage { | |||
| OBJECT_EQUAL_TO("object.equalTo", "\"{0}\" must be equal to {1}"), // | |||
| OBJECT_ONE_OF("object.oneOf", "\"{0}\" must be one of the following values: {1}"), // | |||
| OBJECT_NOT_ONE_OF("object.notOneOf", "\"{0}\" must not be one of the following values: {1}"), // | |||
| OBJECT_ALL_OF("object.allOf", "\"{0}\" must be have of all of the following values: {1}, missing values: {2}"), // | |||
There was a problem hiding this comment.
object. prefix is not correct in this case
@making I followed the test case format already present in the same test file. The use case is simply to verify whether all items from one collection are present in an expected collection. For example, consider a person on vacation with a planned list of places to visit. There might be certain locations they definitely want to visit. This type of validation can be useful in such scenarios. |
|
Thanks for your contribution! |
Adding validation for
allOf