Add validation for keywords related to numbers and strings. It may be surprising that keywords like "minimum" or "minLength" don't imply that the instance is a number or string. But that is how JSON Schema is designed. Change-Id: I8805a5fe91ee345931e1c989f174ea2d0be6665a Reviewed-on: https://go-review.googlesource.com/c/tools/+/667975 Reviewed-by: Robert Findley <rfindley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Jonathan Amsterdam <jba@google.com>
60 lines
1.6 KiB
JSON
60 lines
1.6 KiB
JSON
[
|
|
{
|
|
"description": "maximum validation",
|
|
"schema": {
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"maximum": 3.0
|
|
},
|
|
"tests": [
|
|
{
|
|
"description": "below the maximum is valid",
|
|
"data": 2.6,
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "boundary point is valid",
|
|
"data": 3.0,
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "above the maximum is invalid",
|
|
"data": 3.5,
|
|
"valid": false
|
|
},
|
|
{
|
|
"description": "ignores non-numbers",
|
|
"data": "x",
|
|
"valid": true
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"description": "maximum validation with unsigned integer",
|
|
"schema": {
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"maximum": 300
|
|
},
|
|
"tests": [
|
|
{
|
|
"description": "below the maximum is invalid",
|
|
"data": 299.97,
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "boundary point integer is valid",
|
|
"data": 300,
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "boundary point float is valid",
|
|
"data": 300.00,
|
|
"valid": true
|
|
},
|
|
{
|
|
"description": "above the maximum is invalid",
|
|
"data": 300.5,
|
|
"valid": false
|
|
}
|
|
]
|
|
}
|
|
]
|