-
Notifications
You must be signed in to change notification settings - Fork 69
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
not yet implemented: media type encoding, no schema: MediaType #794
Comments
There are quite a few responses of this form: "responses": {
"200": {
"content": {
"application/json;charset=utf-8": {}
},
"description": ""
}, I'm not entirely sure what to make of these. According to a claim in the OpenAPI repo (that seems to conflict with the actual spec and the topic of binary responses), it's permissible to have an empty or absent Do you happen to know the actual response and/or the intention of the folks who publish this OpenAPI document? |
cc. @roberth |
They're generated by I think it'd be fine for a client to return the non-validated JSON in cases like this. |
It's surprising that a 204 response would contain a Would it be worth filing an issue with servant-openapi3 to change this behavior? If it's a 204 response, there should (I think) be no |
In case it lends any useful context to the above: in trying Progenitor on https://github.com/intercom/Intercom-OpenAPI/blob/main/descriptions/2.11/api.intercom.io.yaml I get,
|
When trying to generate a client from the following json I get the error.
The text was updated successfully, but these errors were encountered: