Sample request body for binary string uses "raw" instead of "binary"

[elazar]

When importing an OpenAPI spec with this request boy specification...

"requestBody": {
  "content": {
    "image/*": {
      "schema": {
        "type": "string",
        "format": "binary"
      }
    }
  },
  "description": "Upload of image file"
}

... the result is that "raw" is selected for the request body type instead of "binary" and a Lorem Ipsum-style string is supplied as the sample request body.

[VShingala]

@elazar Got the issue. Are there any other media types that can show the same behavior? OpenAPI specification only mentions the image as one. (https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#considerations-for-file-uploads)

[elazar]

@VShingala In the context of this issue, images are admittedly the only type I've dealt with.

If your thought is to handle this by content type, I'm not sure there's a reliable way to do so. You can potentially exclude text/* types, but there are others (e.g. application/json) to which I would assume you would not want to apply this new behavior.

Offhand, my suggestion would be to limit the change I'm suggesting to cases where the request body schema contains only a type of string and a format of binary. This can always be expanded later if other use cases surface.

[VShingala]

@elazar This issue is now fixed with latest postman app.