Support documentation for custom parsers

[cyrilchapon]

Hi,

According to akheron/typera#688, I'm leaving a comment here, of a non-working generated OpenAPI with a custom parser (typera-zod).

const updateUserRoute: Route<
  | Response.Ok<UserPayloadDTO>
  // | ... Error types
> = adminRoute
  .put('/user/:id(uuidv4)')
  .use(ZodParser.body<UserUpdatePayloadDTO>(userUpdatePayloadSchema))
  .handler(async (request) => {
    // This is typed correctly
    const userUpdatePayload = request.body

    // ...
  })

Generated OpenAPI :

    '/user/{id}': {
      put: {
        operationId: 'updateUserRoute',
        parameters: [
          {
            name: 'id',
            in: 'path',
            required: true,
            schema: { type: 'string' },
          },
        ],
        responses: {
          '200': {
            description:
// ...

---

The thing is I don't really understand why; since apparently, the strategy is to lookup the type from the request.body variable; and it's correctly typed in my example above.

I can give a shot a fixing, but I'd need help to know where to start. Any idea ? :)

[cyrilchapon]

The trouble were apparently in the building strategy of typera-zod which was somehow broken (or at least breaking something). I was transpiling to an "hybrid" package (CJS + ESM), and apparently typera-openapi was not liking it.

In my last refactor, I turned it to a pure CJS build; which resolves everything and it works like a charm 🎉

Closing this, however it might need investigation to confirm typera-openapi can work with an ESM parser.