-
-
Notifications
You must be signed in to change notification settings - Fork 228
Content type octet-stream #116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@pawamoy what sort of Python type would you expect from an octet-stream. |
Thanks for the quick reply @dbanty! Yeah I guess Feel free to mark this a feature request instead of bug by the way :) |
@emannguitar looking at the example given here, they're using a custom (not part of OpenAPI standard) string format. I believe that would end up being a normal Given that application/octet-stream is supposed to always contain "arbitrary binary data" (source) does it make sense to just always force the BytesResponse for that content type? |
* Added support for octet-stream content type (#116) Co-authored-by: Ethan Mann <[email protected]>
Describe the bug
I'm getting this parsing error:
To Reproduce
I'm not sure I can share the spec here, I will try to clean it up to give you a MRE.
Expected behavior
openapi-python-client
supports theoctet-stream
content-type.OpenAPI Spec File
Same remark as above: I'm not sure I can share the spec here, I will try to clean it up to give you a MRE.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: