val rootSwaggerEndpoints = SwaggerInterpreter().fromServerEndpoints[MyIO](root.all, "My API", "1.0")
val rootEndpoints = root.all ++ rootSwaggerEndpoints
val apiv4SwaggerEndpoints = SwaggerInterpreter(swaggerUIOptions =
).fromServerEndpoints[MyIO](apiv4.all, "My API", "1.0")
val apiv4Endpoints = apiv4.all ++ apiv4SwaggerEndpoints
val rootRoutes: HttpRoutes[MyIO] = ZHttp4sServerInterpreter().from(rootEndpoints).toRoutes
val apiv4Routes: HttpRoutes[MyIO] = ZHttp4sServerInterpreter().from(apiv4Endpoints).toRoutes
val router: HttpRoutes[MyIO] = Router("/" -> rootRoutes, "/api/4" -> apiv4Routes)
This makes it so I have two docs endpoints, one mounted on / and one mounted on /api/4. Is there a nice way to make it so all endpoints appear in /docs, but have the apiv4SwaggerEndpoints have the /api/4/ prefix to them? As you can see, I had to add a contextPath to my apiv4SwaggerEndpoints, as Swagger sent requests to /, even though the docs were on /api/4.
The context path setting is not relevant if you use relative paths. If I understand your desired layout correctly (you want to add a server to openapi which will point to /api/v4), this can be done by modifying the options as follows:
What I’m trying to do is a have a single docs endpoint, to be mounted on the root route (so /docs), and that it will have the endpoints of both screenshots, with routes preceded with /api/4 showing as such in Swagger.
Ah, that _.endpoint.prependIn was what I was missing! Thank you very much, Adam! And while I’m at it, tapir made a great impression at work today, after adding 3 lines of code and getting a documented Swagger UI for free