[zod-openapi]- running middleware after validation about middleware

[yusukebe]

Hi @ivandotv

What is the reasoning behind that decision?

This is to keep the implementation simple. If it allows multiple handlers, the type definition will be very, very complex.

Instead, you may use a Hook:

app.openapi(
  route,
  (c) => {
    const val = c.var.val
    return c.json()
  },
  (result, c) => {
    if (result.success) {
      c.set('val', 'foo')
      // auth
    }
  }
)

[ivandotv]

I believe breaking the middleware contract to have a type inference on the default handler is not worth it.
Open API can also have multiple responses, and putting that logic in one giant function will not work and will not scale.

Breaking the middleware contract (which is used in the original Hono, and other frameworks) is a bad decision

In the end I took the underlying zod-to-openapi package and did the implementation from scratch, respecting the middleware order.

Feel free to close this issue.

[yusukebe]

Breaking the middleware contract (which is used in the original Hono, and other frameworks) is a bad decision

Regarding this "Zod OpenAPI Hono", our first idea is to implement OpenAPI with keeping the RPC feature. So we can't avoid that don't support multiple handlers.

In the end I took the underlying zod-to-openapi package and did the implementation from scratch, respecting the middleware order.

It's a good idea. I think you don't need to use this Zod OpenAPI Hono.

Thanks. Closing the issue.