A way to group features or services to allow middleware to be applied to groups

[dannflor]

A way to group features or services to allow middleware to be applied to groups

[dannflor]

I am aware that middleware could respond in a way that is undocumented, however that was already the case with whatever middleware is placed in front of the single route builder (for instance the request injection middleware could respond with an undocumented response if it pleased).

[czechboy0]

If I understood your ask correctly, you can already achieve this by putting each document into a separate Swift module, and then having your executable attach the generated routes from both OpenAPI docs to the same server.

That would allow you to do exactly this, with two extra imports:

import Admin
import Public

let requestAttached = app.grouped(OpenAPIRequestInjectionMiddleware())

let adminTransport = VaporTransport(routesBuilder: requestAttached.grouped(AdminMiddleware()))
let publicTransport = VaporTransport(routesBuilder: requestAttached)

let adminHandler = AdminAPIProtocolImpl()
let publicHandler = PublicAPIProtocolImpl()

try adminHandler.registerHandlers(on: adminTransport, serverURL: Servers.server1())
try publicHandler.registerHandlers(on: publicTransport, serverURL: Servers.server1())

try await app.execute()

[dannflor]

Thanks for the workaround. Are there any plans to more cleanly support middleware, possibly by allowing the middleware to be documented and have their responses enforced by some sort of protocol as well?

[czechboy0]

Middlewares are a concept of the runtime library, which is shared by all adopters with their OpenAPI docs.

Maybe there could be a concept of a project-specific middleware, but we haven't done any thinking around this area.

Ideas and proposals are always welcome 🙂