Skip to content
This repository was archived by the owner on Nov 3, 2023. It is now read-only.

Commit a080034

Browse files
committed
fixup! Update for new semantics of exclusiveMin/Max
1 parent e9fb5e5 commit a080034

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

source/reference/numeric.rst

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,11 +189,17 @@ While you can specify both of ``minimum`` and ``exclusiveMinimum`` or both of
189189
.. language_specific::
190190

191191
--Draft 4
192-
In JSON Schema Draft 4, ``exclusiveMinimum`` and ``exclusiveMaximum`` work differently. There they are boolean values, that indicate whether ``minimum`` and ``maximum`` are exclusive of the value. For example:
192+
In JSON Schema Draft 4, ``exclusiveMinimum`` and ``exclusiveMaximum`` work
193+
differently. There they are boolean values, that indicate whether
194+
``minimum`` and ``maximum`` are exclusive of the value. For example:
193195

194196
- if ``exclusiveMinimum`` is ``false``, *x* ≥ ``minimum``.
195197
- if ``exclusiveMinimum`` is ``true``, *x* > ``minimum``.
196198

199+
This was changed to have better keyword independence.
200+
201+
Here is an example using the older Draft 4 convention:
202+
197203
.. schema_example:: 4
198204

199205
{

0 commit comments

Comments
 (0)