Skip to content

Remove boolean form of exclusive* keywords. #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 29, 2016
Merged

Remove boolean form of exclusive* keywords. #210

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 7 additions & 19 deletions jsonschema-validation.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,7 +213,6 @@
<list>
<t>"additionalProperties", whose behavior is defined in terms of "properties" and "patternProperties";</t>
<t>"additionalItems", whose behavior is defined in terms of "items"; and</t>
<t>"minimum" and "maximum", whose behavior may change for a special value of "exclusiveMinimum" and "exclusiveMaximum", respectively.</t>
</list>
</t>
</section>
Expand Down Expand Up @@ -248,21 +247,16 @@
The value of "maximum" MUST be a number, representing an inclusive upper limit for a numeric instance.
</t>
<t>
If "exclusiveMaximum" is true, see the validation rules for that keyword instead.
Else if the instance is a number, then this keyword validates only if the instance is less than or exactly equal to "maximum".
If the instance is a number, then this keyword validates only if the instance is less than or exactly equal to "maximum".
</t>
</section>

<section title="exclusiveMaximum">
<t>
The value of "exclusiveMaximum" MUST be number, representing an exclusive upper limit for a numeric instance, or a boolean. Schemas SHOULD NOT use the boolean form.
The value of "exclusiveMaximum" MUST be number, representing an exclusive upper limit for a numeric instance.
</t>
<t>
<cref>The boolean form of "exclusiveMaximum" is expected to be removed in the future.</cref>
</t>
<t>
If "exclusiveMaximum" is true, "maximum" is a number, and the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "maximum".
Else if "exclusiveMaximum" is a number and the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "exclusiveMaximum".
If the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "exclusiveMaximum".
</t>
</section>

Expand All @@ -271,21 +265,16 @@
The value of "minimum" MUST be a number, representing an inclusive upper limit for a numeric instance.
</t>
<t>
If "exclusiveMinimum" is true, see the validation rules for that keyword instead.
Else if the instance is a number, then this keyword validates only if the instance is greater than or exactly equal to "minimum".
If the instance is a number, then this keyword validates only if the instance is greater than or exactly equal to "minimum".
</t>
</section>

<section title="exclusiveMinimum">
<t>
The value of "exclusiveMinimum" MUST be number, representing an exclusive upper limit for a numeric instance, or a boolean. Schemas SHOULD NOT use the boolean form.
</t>
<t>
<cref>The boolean form of "exclusiveMinimum" is expected to be removed in the future.</cref>
The value of "exclusiveMinimum" MUST be number, representing an exclusive upper limit for a numeric instance.
</t>
<t>
If "exclusiveMinimum" is true, "minimum" is a number, and the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "minimum".
Else if "exclusiveMinimum" is a number and the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "exclusiveMinimum".
If the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "exclusiveMinimum".
</t>
</section>

Expand Down Expand Up @@ -691,8 +680,7 @@
"definitions": {
"positiveInteger": {
"type": "integer",
"minimum": 0,
"exclusiveMinimum": true
"exclusiveMinimum": 0,
}
}
}
Expand Down
13 changes: 3 additions & 10 deletions schema.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,22 +54,19 @@
"default": {},
"multipleOf": {
"type": "number",
"minimum": 0,
"exclusiveMinimum": true
"exclusiveMinimum": 0
},
"maximum": {
"type": "number"
},
"exclusiveMaximum": {
"type": "boolean",
"default": false
"type": "number"
},
"minimum": {
"type": "number"
},
"exclusiveMinimum": {
"type": "boolean",
"default": false
"type": "number"
},
"maxLength": { "$ref": "#/definitions/positiveInteger" },
"minLength": { "$ref": "#/definitions/positiveIntegerDefault0" },
Expand Down Expand Up @@ -144,9 +141,5 @@
"oneOf": { "$ref": "#/definitions/schemaArray" },
"not": { "$ref": "#" }
},
"dependencies": {
"exclusiveMaximum": [ "maximum" ],
"exclusiveMinimum": [ "minimum" ]
},
"default": {}
}