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
Swagger-springmvc seems to group swagger "APIs" on a per controller level. But for my usecase to work in swagger I guess it would need to somehow merge both controllers into the "/foo" api. Therefore at the moment only my "root" controllers are browsable in swagger-ui as springmvc does not call the DocumentationController.getApiDocumentation if apiName contains slashes like it would be the case with "/foo/bar".
Is something like this possible with swagger-springmvc? I can't simply merge all controller classes as the web service sports a lot of endpoints that are grouped hierarchically.
The text was updated successfully, but these errors were encountered:
@aeisele currently it does not support your use case. I will say that your need is very specific and may not be prioritized but the library is now extensible so that you could write your own Filters to generate the shape of the documentation you need. There are different extensibility points that allow you to write filters at the documentation, endpoint, operation and even parameter levels that would let you achieve what you need.
Hi,
I have controllers that are mapped like this:
This results in spring endpoints like:
GET /foo
GET /foo/bar
Swagger-springmvc seems to group swagger "APIs" on a per controller level. But for my usecase to work in swagger I guess it would need to somehow merge both controllers into the "/foo" api. Therefore at the moment only my "root" controllers are browsable in swagger-ui as springmvc does not call the
DocumentationController.getApiDocumentation
if apiName contains slashes like it would be the case with "/foo/bar".Is something like this possible with swagger-springmvc? I can't simply merge all controller classes as the web service sports a lot of endpoints that are grouped hierarchically.
The text was updated successfully, but these errors were encountered: