Handling the null type in JSON schema

Swagger 2.0 does not support the null type because Swagger supports only a subset of JSON schema.

If a service that is imported into the API contains nullable fields, as shown in the following example with "type": ["null", "string"], the first supported type (in this example, "string") is used, and only the Remove transform is allowed in the mapping editor.

{
  "type": "object",
  "properties": {
    "location": {
      "type": [
        "null",
        "string"
      ],
      "maxLength": 16
    }
  },
  "required": [
    "LOCATION"
  ]
}

Because Swagger 2.0 does not support the null type, nullable fields are indistinguishable from non-nullable fields in the Swagger document. When null types are sent to the z/OS® Connect server, they are passed through in the body and not represented in the Swagger document.