-
Notifications
You must be signed in to change notification settings - Fork 43
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
Response without schema #71
Comments
I tried exactly the example you've given without seeing the error you have. Using current release |
The code with an empty schema ( The error occurs when trying to omit responses: {
'415': {
description: 'Not supported'
}
} which yields the |
Yes I did observe that error when A curious thing given everything in The same issue would apply when returning |
Thanks for confirming. I agree that it would be good to avoid the error when schema is missing. If there are other ways to skip the schema, I would be open to ideas. |
Is it possible to define a response that has no schema, e.g. for return an error?
Currently, the schema needs to be set, for example like
which renders an empty json object in the schema on the documentation page.
Omitting the schema or setting it to null fails with
It would be nice if one could represent that nothing gets returned.
The text was updated successfully, but these errors were encountered: