Closed olgunkaya closed 9 months ago
We provide swagger at the client side. Our swagger config is microservice aware. Springdoc provided one is not. The springdoc swagger ui makes sense to monolith with skipClient only.
There is a closed bug about this solution. Don't know if we have documentation about this, we could add.
I think, I hit the condition, skipClient and monolith :)
Teşekkürler Olgun Kaya
Marcelo Shima @.***> şunları yazdı (19 Nis 2022 17:42):
We provide swagger at the client side. Our swagger config is microservice aware. Springdoc provided one is not. The springdoc swagger ui makes sense to monolith with skipClient only.
There is a closed bug about this solution. Don't know if we have documentation about this, we could add.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
This issue is stale because it has been open for too long without any activity. Due to the moving nature of jhipster generated application, bugs can become invalid. If this issue still applies please comment otherwise it will be closed in 7 days
Today, I spent considerable amount of time to figure out what's going on with swagger UI and realized that jhipster only includes mvc artifact with the swagger-ui web distro in webapps.
Is there any specific reason to not to go with (link)
but instead go with mvc configurer [ in this link ](https://springdoc.org/#spring-webmvc-support ?
I added the above mentioned ui with proper version (in my case 1.6.6) and now it works, displayes the UI. But not sure if I do this correct/properly.