You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... 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.
The text was updated successfully, but these errors were encountered:
@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.
When importing an OpenAPI spec with this request boy specification...
... 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.
The text was updated successfully, but these errors were encountered: