oneOf is supported in OpenAPI version 3 (openapi: 3.0.0), but not in Swagger version 2 (swagger: ‘2.0’). PaymentMethod: oneOf: – $ref: ‘#/components/schemas/NewPaymentMethod’ – $ref: ‘#/components/schemas/ExistPaymentMethod’ GitHub issue ref: https://github.com/OAI/OpenAPI-Specification/issues/333 For a list of changes in OpenAPI 3.0 compared to 2.0, see: https://blog.readme.io/an-example-filled-guide-to-swagger-3-2/
this is a java issue somewhat I believe. If you debug your program, your Double will always be displayed scientifically, so what we’ll want is to force it into a String. This can be achieved in Java in multiple ways, and you can look it up here: How to print double value without scientific notation … Read more
Like in JSON Schema, OpenAPI schema objects do not require a type, and you are correct in that no type means any type. “Type-specific” keywords such as properties, items, minLength, etc. do not enforce a type on the schema. It works the other way around – when an instance is validated against a schema, these … Read more
I believe what you need to do to achieve this is set additionalProperties to false. See the specification here
Disclaimer: I am the author of Jsonix, a powerful open-source XML<->JSON JavaScript mapping library. Today I’ve released the new version of the Jsonix Schema Compiler, with the new JSON Schema generation feature. Let’s take the Purchase Order schema for example. Here’s a fragment: <xsd:element name=”purchaseOrder” type=”PurchaseOrderType”/> <xsd:complexType name=”PurchaseOrderType”> <xsd:sequence> <xsd:element name=”shipTo” type=”USAddress”/> <xsd:element name=”billTo” type=”USAddress”/> … Read more
[author of the draft v4 validation spec here] You have stumbled upon the most common problem in JSON Schema, that is, its fundamental inability to do inheritance as users expect; but at the same time it is one of its core features. When you do: “allOf”: [ { “schema1”: “here” }, { “schema2”: “here” } … Read more
This is not possible as of OpenAPI 3.1 OpenAPI 3.0/3.1 Specifications currently defines the deepObject behavior only for simple objects (with primitive properties) such as { “id”: 5, “name”: “Bob” } but not for arrays and not for nested objects. Since the behavior for arrays and nested objects is not defined, there’s really no way … Read more
type: object without properties describes a free-form object. So the response schema can be: type: object properties: original: type: object # <———- processed: type: object properties: stdFieldA: type: string stdFieldB: type: string
I searched for the best practice to enforce validation for incoming json data into a RESTful service. My suggestion is to use a MessageBodyReader which performs the validation inside the readFrom method. Below there is an message-body-reader example which is non-generic for the sake of simplicity. I also was interesed in finding the best framework … Read more
Visual Studio 2017 has this feature. From the menu, choose Edit, Paste Special, Paste JSON As Classes. Paste in the JSON and Visual Studio will create the required classes.