Respone data type validation is failing in nested json unless at json level the parameter is marked as mandatory

[joshi-mohit]

e.g
for response as
{"authentication":{"token":"xxx","bid":6,"umail":"[email protected]"}} -- should give error (since bid is specificed as string but actually in data is an integer) for below schema -- but it does not do so. (But if in the below schema if we make either "authentication" as mandatory or we make "token&bid&umail" as mandatory, this detects the error) -- is this right behavior ?

    "responses": {
      "200": {
        "description": "Login sucessful",
        "content": {
          "application/json": {
            "schema": {
              "type": "object",
              "properties": {
                "authentication": {
                  "type": "object",
                  "properties": {
                    "token": {
                      "type": "string"
                    },
                    "bid": {
                      "type": "string"
                    },
                    "umail": {
                      "type": "string",
                      "format": "email"
                    }
                  },
                }
              },
            }
          }
        }
      }
    }

[fenollp]

Indeed this is a bug that the (in progress) switch to gojsonschema fixes.