Using empty schema object does not work anymore

[micovery]

Since this change,

9db746f

It's not possible anymore to specify an empty schema object in a response.

{ }

I believe this is because of the "oneOf" operator:

"oneOf": [
            {
              "$ref": "#/definitions/schema"
            },
            {
              "$ref": "#/definitions/fileSchema"
            }
          ]

since { } matches both schemas ... it fails validation.

A simple fix for this I think is to make the "type" field required for "#/definitions/fileSchema"

[webron]

Thanks for reporting, I'll get it fixed. Do you experience the problem with any specific tool?

[micovery]

I see it as a validation error when using editor.swagger.io.

---
swagger: "2.0"
info:
  title: "Sample"
  version: "1.0.0"
basePath: "/sample"
paths:
  /test:
    get:
      summary: "Test API"
      description: Test API"
      responses:
        200:
          schema: { }
          description: "Operation Successful"

[webron]

Okay thanks. Keep in mind it'll take a bit for the fix to be included in the editor.

In general, we don't recommend using an empty schema, however it is valid.

[achew22]

This doesn't seem to be fixed on http://editor.swagger.io on Sunday December 27th 2015. Is that working as intended? Using the same code sample referenced above.