I am using json-schema and wanting to only allow properties that are declared in this file to pass validation. For instance if a user passes a "name" property in their json object it will fail this schema because "name" is not listed here as a property.
Is there some function similar to "required" that will only allow the listed properties to pass?
{
"$schema": "http://json-schema.org/draft-04/schema#",
"title": "Accounting Resource - Add Item",
"type": "object",
"properties": {
"itemNumber": {
"type":"string",
"minimum": 3
},
"title": {
"type":"string",
"minimum": 5
},
"description": {
"type":"string",
"minimum": 5
}
},
"required": [
"itemNumber",
"title",
"description"
]
}
Properties. The properties (key-value pairs) on an object are defined using the properties keyword. The value of properties is an object, where each key is the name of a property and each value is a schema used to validate that property.
Gets or sets a flag indicating whether the value can not equal the number defined by the minimum attribute (Minimum).
JSON Schema Example A little description of the schema. The type keyword defines the first constraint on our JSON data: it has to be a JSON Object. Defines various keys and their value types, minimum and maximum values to be used in JSON file. This keeps a list of required properties.
The property keyword is used to specify the key:value pairs of JSON documents.
I believe what you need to do to achieve this is set additionalProperties
to false. See the specification here
Inside your definition provide:
"required": []
"additionalProperties": false
DEMO:
without "additionalProperties": false
:
with "additionalProperties": false
:
FYI - it looks like v5 of the standard will describe a "ban unknown properties" validation mode.
So instead of making this requirement part of the format (which as Chris Pitman says in the comments, damages future extensibility), you can simply instruct your validator to flag unknown properties as errors. So, it's like a super-strict validation mode which is useful for dev.
Some validators already support this (e.g. tv4):
var result = tv4.validateMultiple(data, schema, checkRecursive, banUnknownProperties);
With this tool, checkRecursive
should be used if your data might have circular references, and banUnknownProperties
will do exactly what you want, without having to use "additionalProperties":false
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With