Support multiple OpenAPI definitions in one procedure

[dcramer]

.route is supported to overload a previous called procedure, but what would be really amazing is the ability to define multiple openapi endpoints per-procedure. This simplifies some code reusability, as for a real world example, I have a comments endpoint that I need three different variations of (two for ergonics, and one for administrative "query all" purposes):

export default procedure
  .route({
    method: "GET",
    path: "/comments",
    tags: ["admin"],
  })
  .route({
    method: "GET",
    path: "/tastings/:tasting/comments",
    tags: ["tastings"],
  })
  .route({ method: "GET", path: "/users/:user/comments", tags: ["users"] })
  .input(
    z.object({
      user: z.union([z.literal("me"), z.coerce.number()]).optional(),
      tasting: z.coerce.number().optional(),
      cursor: z.coerce.number().gte(1).default(1),
      limit: z.coerce.number().gte(1).lte(100).default(100),
    }),
  )
  .output(
    z.object({
      results: z.array(CommentSchema),
      rel: CursorSchema,
    }),
  )
  .handler(async function ({ input, context, errors });

I have often built procedures like this, and then you end up exporting them, reimporting them, defining a new duplicate endpoint that only calls e.g. one of the params. oRPC is so close to avoiding any of that boilerplate, and in this case its literally just metadata.

[dinwwwh]

Someone looking for a temporary solution it here:

const procedure = os.input(..).output(...).handler(...)

const router = {
    admin: {
        procedure: procedure.route({ method: 'GET', path: '/admin/commnets' })
   },
    tasting: {
        procedure: procedure.route({ method: 'GET', path: '/tastings/commnets' })
   }
}

WARNING: You can cannot make parameter be optional tasting: z.coerce.number().optional() so this just temporary solution but it will not work in OP example, for the case like this I recommend create two procedure, one call another

[dinwwwh]

There are no plans to support this feature. Instead, you can redefine the same procedure multiple times in a router with different .route definitions. When duplicate routes exist, the later .route definition overrides or merged with the earlier one.