Inconsistent knownMediaType produced for "type": "string", "format": "binary" json values

[pakrym]

{
  "swagger": "2.0",
  "info": {
    "title": "JsonAsBinary",
    "description": "JsonAsBinary",
    "version": "1.0.0"
  },
  "host": "localhost:3000",
  "schemes": [
    "http"
  ],
  "produces": [
    "application/json"
  ],
  "consumes": [
    "application/json"
  ],
  "paths": {
    "/Operation/": {
      "put": {
        "operationId": "Operation",
        "parameters": [
          {
            "name": "body",
            "in": "body",
            "schema": {
              "type": "string",
              "format": "binary"
            }
          }
        ],
        "responses": {
          "200": {
            "description": "",
            "schema": {
              "type": "string",
              "format": "binary"
            }
          }
        }
      }
    }
  }
}

       protocol: !<!Protocols> 
              http: !<!HttpWithBodyRequest> 
                path: /Operation/
                method: put
                knownMediaType: json <----------
                mediaTypes:
                  - application/json
                uri: '{$host}'
        signatureParameters: []
        responses:
          - !<!BinaryResponse> 
            binary: true
            language: !<!Languages> 
              default:
                name: ''
                description: ''
            protocol: !<!Protocols> 
              http: !<!HttpBinaryResponse> 
                knownMediaType: binary <----------
                mediaTypes:
                  - application/json
                statusCodes:
                  - '200'

[daviwil]

Basically the request here is to add support for having a consumes of application/json which can have a parameter of type: string, format: binary (or type: file, format: object in Swagger) which produces a code model that sets KnownMediaType: binary for the parameter to be expressed as a stream even though the service expects JSON.