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
Also webjars/swagger-ui library bring this feature with 5.4.2 version; webjars/swagger-ui#196
But when i looked the pom, i saw latest version of (2.2.0) uses 5.2.0 version of webjars/swagger-ui library.
But this feature came with 5.4.2 release so could you update webjars/swagger-ui dependency version please?
Describe alternatives you've considered
I tried to override webjars dependency version like below;
But somehow swagger-ui docs doesn't generated. Because i can't see any logs for "docs generated" like before.
Also when i try to call swagger ui link it gives me 404 Not Found.
But i don't know why this is happening.
Additional context
Example code, i needed boundary specific content type;
Is your feature request related to a problem? Please describe.
Hello,
Latest version (2.2.0) of springdoc-openapi-starter-webmvc-ui library doesn't support content type for multipart requests.
This problem already addressed below;
#820 (comment)
Swagger UI finally fixed these issues.
This is the issue;
swagger-api/swagger-ui#5356 (comment)
And this is the pull request;
swagger-api/swagger-ui#9105
Also webjars/swagger-ui library bring this feature with 5.4.2 version;
webjars/swagger-ui#196
But when i looked the pom, i saw latest version of (2.2.0) uses 5.2.0 version of webjars/swagger-ui library.
But this feature came with 5.4.2 release so could you update webjars/swagger-ui dependency version please?
Describe alternatives you've considered
I tried to override webjars dependency version like below;
But somehow swagger-ui docs doesn't generated. Because i can't see any logs for "docs generated" like before.
Also when i try to call swagger ui link it gives me 404 Not Found.
But i don't know why this is happening.
Additional context
Example code, i needed boundary specific content type;
The text was updated successfully, but these errors were encountered: