-
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 schema for mutipart/form-data object properties #9756
Comments
As it's not officially supported, I have to do it myself. My solution is simple and just show the example value like clicking "Try it out". Even though it's not as fancy as your example, it's better than nothing. |
Need it + 1 |
The change can be checked for a better handling now in: https://github.com/kenspirit/swagger-ui/tree/multipart-body-show-schema |
same problem here |
Content & configuration
Swagger/OpenAPI definition:
Is your feature request related to a problem?
In the example provided the 'metadata' which is an object property property is defined using a schema.
After clicking on 'Try it out' an example based on this schema is displayed, however the schema is not displayed in Swagger UI.
Consequently :
As API provider I have to provide a link in description to inform consummer that the json for the property should follow the schema
As API consumer I have to scroll down to the bottom of the OAS definition to display the schema.
Describe the solution you'd like
With the impovement, for each obect property, the user is allowed to choose between 'Example value' and 'Schema'
Describe alternatives you've considered
Current solution : Add link to the schema in endpoint's description
Additional context
The purpose of this endpoint is to offer a versatile method for uploading files and associated metadata of various types. The set of metadata required depends on the nature of the file, such as Invoicing or Identification documents (see Schemas for examples).
Related issues :
-> Is asking to show a preview of the payload (an example) without clicking on "Try it out"
-> Is asking the same as this one but for query parameters
-> Same as 4581
The text was updated successfully, but these errors were encountered: