On json-schema.org you will find something appropriate in the File System Example section. You can define patternProperties inside an object. { “type”: “object”, “properties”: { “/”: {} }, “patternProperties”: { “^(label_name_[0-9]+)+$”: { “type”: “integer” } }, “additionalProperties”: false, } The regular expression (label_name_[0-9]+)+ should fit your needs. In JSON Schema regular expressions are explicitly anchored … Read more
Another option which supports generating JSON Schema v4 is NJsonSchema: var schema = JsonSchema.FromType<Person>(); var schemaJson = schema.ToJson(); The library can be installed via NuGet. Update for NJsonSchema v9.4.3+: using NJsonSchema; var schema = await JsonSchema.FromTypeAsync<Person>(); var schemaJson = schema.ToJson();
Try this: { “description” : “schema validating people and vehicles”, “type” : “object”, “oneOf” : [ { “type” : “object”, “properties” : { “firstName” : { “type” : “string” }, “lastName” : { “type” : “string” }, “sport” : { “type” : “string” } } }, { “type” : “object”, “properties” : { “vehicle” : … Read more
EDIT: as pointed out by commenters, module is being deprecated, not maintained. So, Caveat Emptor etc One such tool is Jackson JSON Schema module: https://github.com/FasterXML/jackson-module-jsonSchema which uses Jackson databind’s POJO introspection to traverse POJO properties, taking into account Jackson annotations, and produces a JSON Schema object, which may then be serialized as JSON or used … Read more
The IETF draft v4 of the JSON schema only defines required and does not include optional. To quote the section on required from draft v4: Valid values: The value of this keyword MUST be an array. This array MUST have at least one element. Elements of this array MUST be strings, and MUST be unique. … Read more
You can create a json-schema and use the option: additionalProperties = false That way you only allow the attributes defined in properties. In your case: { “properties”: { “fname”: {“type”: “string”}, “lname”: {“type”: “string”}, “age”: {“type”: “string”} }, “additionalProperties”: false }
You can just use the “minProperties” property instead of explicity naming all the fields. { “type”: “object”, “properties”: { “elephant”: {“type”: “string”}, “giraffe”: {“type”: “string”}, “polarBear”: {“type”: “string”} }, “additionalProperties”: false, “minProperties”: 3 }
Use patternProperties instead of properties. In the example below, the pattern match regex .* accepts any property name and I am allowing types of string or null only by using “additionalProperties”: false. “patternProperties”: { “^.*$”: { “anyOf”: [ {“type”: “string”}, {“type”: “null”} ] } }, “additionalProperties”: false … or if you just want to allow … Read more
To set the minimum # of item in an array, use the “minItems”. See: https://datatracker.ietf.org/doc/html/draft-fge-json-schema-validation-00#section-5.3.3 and http://jsonary.com/documentation/json-schema/?section=keywords/Array%20validation { “$schema”: “http://json-schema.org/draft-04/schema#”, “title”: “Product”, “description”: “A product from Acme’s catalog”, “type”: “object”, “properties”: { … “tags”: { “type”: “array”, “items”: { “type”: “string” }, “minItems”: 1, “maxItems”: 4, “uniqueItems”: true } }, “required”: [“id”, “name”, “price”] }
Arnaud in the comments is correct that there are two separate questions here. Do you want to validate that your spec is a valid OpenAPI (fka. Swagger) spec You can Copy your spec to the online Swagger editor and it will throw errors. A quick dive through the source doesn’t tell me what it’s using … Read more