feat: implement number range constraints

Author: mstream

docs/src/examples/json-schema-change-compatibility-checks.md

@@ -41,6 +41,9 @@ Examples:
 - [the new value of multipleOf is divisible by the old one](#the-new-value-of-multipleof-is-divisible-by-the-old-one)
 - [the old value of multipleOf is divisible by the new one](#the-old-value-of-multipleof-is-divisible-by-the-new-one)
 - [old and new value of multipleOf are not each other's factors](#old-and-new-value-of-multipleof-are-not-each-other's-factors)
+- [the range of allowed number values gets extended](#the-range-of-allowed-number-values-gets-extended)
+- [the range of allowed number values gets reduced](#the-range-of-allowed-number-values-gets-reduced)
+- [the range of allowed number values gets extended and reduced at the same time](#the-range-of-allowed-number-values-gets-extended-and-reduced-at-the-same-time)
 ---
 ### No JSON schema differences
 When there is not JSON schema differences, schema change is fully compatible.
@@ -267,3 +270,57 @@ In this situation, there are potentially some numbers that are not divisible by
 ```
 none
 ```
+---
+### the range of allowed number values gets extended
+In this situation, all numbers from the new, longer range fall into the old, shorter range. Therefore, such a change is backward compatible.
+
+#### Input
+##### JSON schema differences
+```
+-
+  Schema path: #
+  maximum changed from 15.0to20.0
+-
+  Schema path: #
+  minimum changed from 10.0to5.0
+```
+#### Output
+```
+backward
+```
+---
+### the range of allowed number values gets reduced
+In this situation, all numbers from the new, shorted range fall into the old, longer range. Therefore, such a change is forward compatible.
+
+#### Input
+##### JSON schema differences
+```
+-
+  Schema path: #
+  maximum changed from 20.0to15.0
+-
+  Schema path: #
+  minimum changed from 5.0to10.0
+```
+#### Output
+```
+forward
+```
+---
+### the range of allowed number values gets extended and reduced at the same time
+In this situation, there are some numbers which do not fall into neither old nor new range. Therefore, such a change is incompatible.
+
+#### Input
+##### JSON schema differences
+```
+-
+  Schema path: #
+  maximum changed from 15.0to20.0
+-
+  Schema path: #
+  minimum changed from 5.0to10.0
+```
+#### Output
+```
+none
+```

docs/src/examples/json-schema-difference-calculation.md

@@ -8,6 +8,10 @@ Examples:
 - [Comparing identical schemata](#comparing-identical-schemata)
 - [Changing expected JSON value type from null to boolean](#changing-expected-json-value-type-from-null-to-boolean)
 - [Changing multipleOf value](#changing-multipleof-value)
+- [Changing exclusiveMaximum value](#changing-exclusivemaximum-value)
+- [Changing exclusiveMinimum value](#changing-exclusiveminimum-value)
+- [Changing maximum value](#changing-maximum-value)
+- [Changing minimum value](#changing-minimum-value)
 ---
 ### Comparing identical schemata
 When two identical schemata are compared, no difference should be found.
@@ -41,7 +45,7 @@ Any change in expected JSON value type should be accounted as a difference.
 #### Output
 ```
 -
-  Schema path: #
+  Schema path: #/type
   Change of accepted JSON value types from 
   - null
   to
@@ -54,15 +58,91 @@ TODO
 #### Input
 ##### Previous JSON schema
 ```json
-{"multipleOf":2,"type":["number"]}
+{"multipleOf":2}
 ```
 ##### Next JSON schema
 ```json
-{"multipleOf":4,"type":["number"]}
+{"multipleOf":4}
 ```
 #### Output
 ```
 -
-  Schema path: #
+  Schema path: #/multipleOf
   multipleOf changed from 2.0 to 4.0
 ```
+---
+### Changing exclusiveMaximum value
+TODO
+
+#### Input
+##### Previous JSON schema
+```json
+{"exclusiveMaximum":2}
+```
+##### Next JSON schema
+```json
+{"exclusiveMaximum":4}
+```
+#### Output
+```
+-
+  Schema path: #/exclusiveMaximum
+  exclusiveMaximum changed from 2.0to4.0
+```
+---
+### Changing exclusiveMinimum value
+TODO
+
+#### Input
+##### Previous JSON schema
+```json
+{"exclusiveMinimum":2}
+```
+##### Next JSON schema
+```json
+{"exclusiveMinimum":4}
+```
+#### Output
+```
+-
+  Schema path: #/exclusiveMinimum
+  exclusiveMinimum changed from 2.0to4.0
+```
+---
+### Changing maximum value
+TODO
+
+#### Input
+##### Previous JSON schema
+```json
+{"maximum":2}
+```
+##### Next JSON schema
+```json
+{"maximum":4}
+```
+#### Output
+```
+-
+  Schema path: #/maximum
+  maximum changed from 2.0to4.0
+```
+---
+### Changing minimum value
+TODO
+
+#### Input
+##### Previous JSON schema
+```json
+{"minimum":2}
+```
+##### Next JSON schema
+```json
+{"minimum":4}
+```
+#### Output
+```
+-
+  Schema path: #/minimum
+  minimum changed from 2.0to4.0
+```

docs/src/examples/json-values-validation.md

@@ -14,6 +14,14 @@ Examples:
 - [An array with forbidden duplicate value.](#an-array-with-forbidden-duplicate-value.)
 - [Number 7.5 against a schema accepting only multiples of 2.5](#number-7.5-against-a-schema-accepting-only-multiples-of-2.5)
 - [Number 7 against a schema accepting only multiples of 2.5](#number-7-against-a-schema-accepting-only-multiples-of-2.5)
+- [A JSON number value is matches exactly the maximum keyword value](#a-json-number-value-is-matches-exactly-the-maximum-keyword-value)
+- [A JSON number value is greater than the maximum keyword value](#a-json-number-value-is-greater-than-the-maximum-keyword-value)
+- [A JSON number value is less than the exclusiveMaximum keyword value](#a-json-number-value-is-less-than-the-exclusivemaximum-keyword-value)
+- [A JSON number value is matches exactly the exclusiveMaximum keyword value](#a-json-number-value-is-matches-exactly-the-exclusivemaximum-keyword-value)
+- [A JSON number value is matches exactly the minimum keyword value](#a-json-number-value-is-matches-exactly-the-minimum-keyword-value)
+- [A JSON number value is less than the minimum keyword value](#a-json-number-value-is-less-than-the-minimum-keyword-value)
+- [A JSON number value is greater than the exclusiveMinimum keyword value](#a-json-number-value-is-greater-than-the-exclusiveminimum-keyword-value)
+- [A JSON number value is matches exactly the exclusiveMinimum keyword value](#a-json-number-value-is-matches-exactly-the-exclusiveminimum-keyword-value)
 ---
 ### A null value against a schema accepting only null values
 A null value conforms to the schema.
@@ -209,3 +217,151 @@ Number 7 does not conform the schema as 7.5 is not a multiple of 2.5.
   JSON path: $
   7.0 is not a multiple of 2.5
 ```
+---
+### A JSON number value is matches exactly the maximum keyword value
+Because maximum constraint is inclusive, such a value is valid.
+
+#### Input
+##### JSON schema
+```json
+{"maximum":4}
+```
+##### JSON
+```json
+4
+```
+#### Output
+```
+✓ no violations
+```
+---
+### A JSON number value is greater than the maximum keyword value
+Because the value is out of the valid range, it is invalid.
+
+#### Input
+##### JSON schema
+```json
+{"maximum":4}
+```
+##### JSON
+```json
+5
+```
+#### Output
+```
+✗
+  Schema path: #/maximum
+  JSON path: $
+  5.0 is outside of the valid range of (-Infinity,4.0]
+```
+---
+### A JSON number value is less than the exclusiveMaximum keyword value
+Because the value is within the valid range, it is valid.
+
+#### Input
+##### JSON schema
+```json
+{"exclusiveMaximum":4}
+```
+##### JSON
+```json
+3
+```
+#### Output
+```
+✓ no violations
+```
+---
+### A JSON number value is matches exactly the exclusiveMaximum keyword value
+Because the exclusiveMaximum constraint is exclusive, such a value is invalid.
+
+#### Input
+##### JSON schema
+```json
+{"exclusiveMaximum":4}
+```
+##### JSON
+```json
+4
+```
+#### Output
+```
+✗
+  Schema path: #/exclusiveMaximum
+  JSON path: $
+  4.0 is outside of the valid range of (-Infinity,4.0)
+```
+---
+### A JSON number value is matches exactly the minimum keyword value
+Because the minimum constraint is inclusive, such a value is invalid.
+
+#### Input
+##### JSON schema
+```json
+{"minimum":4}
+```
+##### JSON
+```json
+4
+```
+#### Output
+```
+✓ no violations
+```
+---
+### A JSON number value is less than the minimum keyword value
+Because the value is out of the valid range, it is invalid.
+
+#### Input
+##### JSON schema
+```json
+{"minimum":4}
+```
+##### JSON
+```json
+3
+```
+#### Output
+```
+✗
+  Schema path: #/minimum
+  JSON path: $
+  3.0 is outside of the valid range of [4.0,Infinity)
+```
+---
+### A JSON number value is greater than the exclusiveMinimum keyword value
+Because the value is within the valid range, it is valid.
+
+#### Input
+##### JSON schema
+```json
+{"exclusiveMinimum":4}
+```
+##### JSON
+```json
+5
+```
+#### Output
+```
+✓ no violations
+```
+---
+### A JSON number value is matches exactly the exclusiveMinimum keyword value
+Because the exclusiveMinimum constraint is exclusive, such a value is not valid.
+
+#### Input
+##### JSON schema
+```json
+{"exclusiveMinimum":4}
+```
+##### JSON
+```json
+4
+```
+#### Output
+```
+✗
+  Schema path: #/exclusiveMinimum
+  JSON path: $
+  4.0 is outside of the valid range of (4.0,Infinity)
+```

src/purs/JsonSchema.purs

@@ -26,7 +26,11 @@ instance Show JsonSchema where
   show schema = genericShow schema
 
 type Keywords =
-  { items ∷ Maybe JsonSchema
+  { exclusiveMaximum ∷ Maybe Number
+  , exclusiveMinimum ∷ Maybe Number
+  , items ∷ Maybe JsonSchema
+  , maximum ∷ Maybe Number
+  , minimum ∷ Maybe Number
   , multipleOf ∷ Maybe Number
   , not ∷ Maybe JsonSchema
   , required ∷ Set String
@@ -36,7 +40,11 @@ type Keywords =
 
 defaultKeywords ∷ Keywords
 defaultKeywords =
-  { items: Nothing
+  { exclusiveMaximum: Nothing
+  , exclusiveMinimum: Nothing
+  , items: Nothing
+  , maximum: Nothing
+  , minimum: Nothing
   , multipleOf: Nothing
   , not: Nothing
   , required: Set.empty