From 3a4060139afcb7b908a6ea52b8f83f4fdc6e8a26 Mon Sep 17 00:00:00 2001 From: Atanas Angelov Date: Tue, 23 May 2017 09:49:49 +0300 Subject: [PATCH] add INCLUDES/EXCLUDES conditional logic operators --- documentation/2-fields/1-usage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/2-fields/1-usage.md b/documentation/2-fields/1-usage.md index f8286f2..9c966ed 100644 --- a/documentation/2-fields/1-usage.md +++ b/documentation/2-fields/1-usage.md @@ -79,8 +79,8 @@ The conditional rules are passed in a two-dimensional array and each rule can ha | Key | Description | Type/Value | Required | | --------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------| -------- | | `field` | The field name to which the rule is applied. The name should be the same as defined in the container. | `string` | Yes | -| `value` | The value of the field. It can be an array only when compare is IN or NOT IN. | `string|array`, default: `""` | No | -| `compare` | Operator to test. Possible values are: =, <, >, <=, >=, IN, NOT IN. | `string`, default: `=` | No | +| `value` | The value of the field. It can be an array only when compare is IN, NOT IN, INCLUDES or EXCLUDES. | `string|array`, default: `""` | No | +| `compare` | Operator to test. Possible values are: =, <, >, <=, >=, IN, NOT IN, INCLUDES or EXCLUDES. | `string`, default: `=` | No | You can optionally pass the `relation` key and set it to either `AND` (default) or `OR`. It defines the relation, when there is more than one rule.