We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I am trying to describe the parameters for an API endpoint, which is supposed to serve file uploads. My docstring looks like
async def handle_upload(self, request: web.Request) -> web.Response: """ --- description: This end-point allows to upload files to the storage service. tags: - Upload produces: - application/json parameters: [] requestBody: required: true content: multipart/form-data: schema: type: object required: - payload properties: payload: type: string format: binary description: the content of the file to be uploaded name: type: string description: the file name (if unset then will be retrieved from `content-disposition` header) responses: "201": description: successful operation ...
Although the generated Swagger document looks like
and does not contain any controls, which would allow file upload.
My question is whether such format supported by the library? Should I, probably, use another approach to describe multipart/form-data content?
The text was updated successfully, but these errors were encountered:
Just checking if there is any update on supporting "Multipart forms" in the library?
Sorry, something went wrong.
No branches or pull requests
Hello,
I am trying to describe the parameters for an API endpoint, which is supposed to serve file uploads. My docstring looks like
Although the generated Swagger document looks like
and does not contain any controls, which would allow file upload.
My question is whether such format supported by the library? Should I, probably, use another approach to describe multipart/form-data content?
The text was updated successfully, but these errors were encountered: