Also allow empty "dependencies" array.

Same rationale as for empty "requirements."
json-schema-org · Nov 11, 2016 · 42f2a31 · 42f2a31
1 parent ac8e207
commit 42f2a31
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 7 deletions.
diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
@@ -524,9 +524,9 @@
                     against the entire instance.
                 </t>
                 <t>
-                    If the dependency value is an array, it MUST have at least one element, each
-                    element MUST be a string, and elements in the array MUST be unique. If the
-                    dependency key is a property in the instance, each of the items in the dependency
+                    If the dependency value is an array, each element MUST be a string,
+                    and elements in the array MUST be unique. If the dependency key is
+                    a property in the instance, each of the items in the dependency
                     value must be a property that exists in the instance.
                 </t>
             </section>

diff --git a/schema.json b/schema.json
@@ -22,9 +22,6 @@
             "type": "array",
             "items": { "type": "string" },
             "uniqueItems": true
-        },
-        "nonEmptyStringArray": {
-            "allOf": [ { "$ref": "#/definitions/stringArray" }, { "minItems": 1 } ]
         }
     },
     "type": "object",
@@ -120,7 +117,7 @@
             "additionalProperties": {
                 "anyOf": [
                     { "$ref": "#" },
-                    { "$ref": "#/definitions/nonEmptyStringArray" }
+                    { "$ref": "#/definitions/stringArray" }
                 ]
             }
         },