-
Notifications
You must be signed in to change notification settings - Fork 190
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
Add a sample for describing a multipart/form-data endpoint for file uploads #18
Comments
It's not currently supported yet, but it will be implemented. |
Any update on this? I would really need it :) |
Are there any updates on when it will be implemented? |
We are in need of this - when would this be available? |
Why is this issue closed? Of course, with 0.9.0-preview you support now byte[] and multiform/form-data. But the issue was created to ask for a sample how to use it. |
@agravity-philipp Good point! I'll update the content for it. |
Thank you @justinyoo - how will I know when this will be available? |
Soon! In the meantime, please find this repo as an example: https://github.com/devkimchi/azure-functions-binary-data-via-swagger-ui This sample app will be used for the document. |
Hi @justinyoo, thanks for your example. I think is missing one for multiple file uploads. I changed the model type from FileModel to List but it shows the ui as the Content-Type was json. Is there any way to make it work? |
Hi @justinyoo, may I know if "Content-Type" : "multipart/form-data" supported for azure rest api's ....? |
Hi @justinyoo, do you have any updates regarding the issue with uploading multiple files? Currently, when providing byte[] it only populates one file upload section in swagger. Is there a possibility to use IFormFile or IFormFileCollection instead of byte[]? |
I'm not sure what the bodyType would be for an endpoint that accepts multipart/form-data using the OpenApiRequestBodyAttribute.
The text was updated successfully, but these errors were encountered: