You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what you expected to happen.
When trying out the API in Swagger UI - I should be able to pass in the request body.
Screenshots
This is a screenshot of the resource in Swagger-UI with springdoc-openapi-ui v1.3.0:
This is a screenshot of the resource in Swagger-UI with springdoc-openapi-ui v1.3.1 and above:
The section for the request body is missing... Additional context
none
The text was updated successfully, but these errors were encountered:
For your case, because if you are using @RequestBody spring annotation before the parameter, it shouldn't be ignored as its required by default.
So the behaviour you are expecting will be out of the box, starting from the next release v1.3.5.
Describe the bug
Given a ressource that excpects a request body of the following type:
@RequestBody HashMap<String, String> body
The Request Body is not available in the Swagger-UI for the resource since springdoc-openapi-ui 1.3.1
But it works in springdoc-openapi-ui 1.3.0
To Reproduce
Steps to reproduce the behavior:
What version of spring-boot you are using?
Spring Boot 2.2.6
What modules and versions of springdoc-openapi are you using?
1.3.1 (also tested with 1.3.4 - same issue)
What is the actual and the expected result using OpenAPI Description (yml or json)?
the requestbody is not available in the UI - but it should be. The generated api docs is the same for springdoc-openapi-ui 1.3.0 and 1.3.1
Expected behavior
When trying out the API in Swagger UI - I should be able to pass in the request body.
Screenshots
This is a screenshot of the resource in Swagger-UI with springdoc-openapi-ui v1.3.0:
This is a screenshot of the resource in Swagger-UI with springdoc-openapi-ui v1.3.1 and above:
The section for the request body is missing...
Additional context
none
The text was updated successfully, but these errors were encountered: