Feature Request: Disable output validation for better performance

[valerii15298]

Currently I did not find a way to disable output validation when using zod schema(or any other schema) for output. Output schema is needed for OpenAPI. But for very large responses validating output(I tested with zod) takes significant slowdown. Zod also deeply clones data when performs parsing.

Would be nice to have a flag to disable output validation for better performance when having large responses.
And by having this option would be also discouraging to use zod .transoform or .owerwrite utilities.

[unnoq]

I think you can do this with clientInterceptors like this (WARNING THIS JUST DRAFT, CAN IMPROVE, MAYBE BUG)

const DISABLED_VALIDATION_SYMBOL = Symbol('DISABLED_VALIDATION')

const rpcHandler = new RPCHandler(router, {
  clientInterceptors: [
    async (options) => {
      if (options.procedure['~orpc'].outputSchema && !(options as any).procedure['~orpc'].outputSchema[DISABLED_VALIDATION_SYMBOL]) {
        options.procedure['~orpc'].outputSchema = new Proxy(options.procedure['~orpc'].outputSchema, {
          get: (target, prop) => {
            if (prop === DISABLED_VALIDATION_SYMBOL) {
              return true
            }

            if (prop === '~standard') {
              return new Proxy(target['~standard'], {
                get: (target, prop) => {
                  if (prop === 'validate') {
                    return (value: any) => ({ value })
                  }

                  return Reflect.get(target, prop)
                },
              })
            }

            return Reflect.get(target, prop)
          },
        })
      }

      return options.next()
    },
  ],
})

[hrmcdonald]

Might be worth mentioning that I think you can also achieve this by just defining your outputs with the type() utility as the inferred zod result type instead of as the schema itself:

  .output(type<z.infer<typeof selectWithRelationsSchema>>()),

I get it's not exactly the same and might not be what you were looking for, but mentioning this here incase it helps anyone else find this option.

But maybe this route doesn't emit the right spec output you were looking for? If so I guess that'd lead you to open this thread.

[roErlend]

Are there any plans for adding this feature in the future? (without my own clientInterceptor)

[theoludwig]

Related issue #481 which also complains about the runtime performance of running validation when it's not necessary.

[unnoq]

Official guide for disabling output validation