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
Swagger/OpenAPI definition:
openapi: 3.1.0 info: title: Test version: '0.0.1' paths: /example: post: summary: Example endpoint operationId: example_endpoint parameters: [] requestBody: required: true content: multipart/form-data: schema: type: object required: - required_field properties: required_field: type: string minLength: 1 optional_field: type: string example: required_field: foo responses: "200": description: OK
Swagger-UI configuration options:
SwaggerUI({ // I am using https://editor-next.swagger.io/ })
Clicking the "Try it out" button for my example endpoint gives the following initial form state:
Instead of using the example provided.
I would like the initial form state to be the following
(required_field="foo" and optional_field omitted) to reflect the example given.
I've played around with different ways of specifying the request body and the example. Nothing seems to produce this result in the swagger UI.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Content & configuration
Swagger/OpenAPI definition:
Swagger-UI configuration options:
Is your feature request related to a problem?
Clicking the "Try it out" button for my example endpoint gives the following initial form state:
Instead of using the example provided.
Describe the solution you'd like
I would like the initial form state to be the following
(required_field="foo" and optional_field omitted) to reflect the example given.
Describe alternatives you've considered
I've played around with different ways of specifying the request body and the example. Nothing seems to produce this result in the swagger UI.
The text was updated successfully, but these errors were encountered: