-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Display static documentation information for multipart properties in OpenAPI 3.0 files #5169
Comments
Possibly related (or duplicate): #4581 |
@hkosova very closely related indeed, but this is for |
Hi all! Do you have any updates on that issue? |
Any updates? That's a bad limitation currently. |
any updates on this? |
Somewhere between 3.32.5 and 3.42.0 it doesn't even display any json in the try it now textbox any more. Multipart support seems to be lagging behind the standard quite a bit now. Multipart is extremely useful for sending object data + file data, which is actually a fairly common scenario. This actually worked better back in 3.16.0 with the v2 spec. Is there a roadmap to improve the multipart experience? |
Any updates?? |
Need this too! |
Is there any workaround or other way as its looks very bad experience |
@jalagari at the moment I provide a sample JSON in the endpoint's description directly |
Are there plans to make this happen? |
Any updates on this? |
Hello everyone, i made a quick fix for this issue, regarding documentation of the multipart/form properties, on my fork. https://github.com/charalarg/swagger-ui. You can see the result on the readme file. |
Hello everyone, any updates on this issue? |
Hello. Any update on this? |
Hello, it's really needed Else i need go to bottom of swagger page and see schema in schema repository there. |
Still needed, so +1 |
I have a simple change that can help on this. |
neet it + 1 |
Would still like to see this implemented. +1 |
Following on from #5164, I am suggesting that for specs with multipart/form-data that we allow the main request body of the spec to show a preview of the payload, rather than leaving it blank (and appearing unrendered) like so:


For "Try it now" feature it appears rendered correctly:
I am proposing something similar to the above pic, even if text areas/drop-downs appear greyed out. Attached following spec as an example which highlights what I thought was an issue, but turns out to be a feature:
v3.20.2_multipart_snippet.txt
Cheers, Rich
The text was updated successfully, but these errors were encountered: