Menü
Disable output validation for improved performance while keeping OpenAPI spec generation.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Quick reference for Better Notify configuration, patterns, and common gotchas
Interactive setup wizard for adding Better Notify to a TypeScript/JavaScript project
Context and API guidance for Better Notify — end-to-end typed notification infrastructure for Node.js
Seamlessly use AI SDK inside your oRPC projects without any extra overhead.
Use oRPC inside an Astro project.
Functions to encode and decode base64url strings (URL-safe variant of base64).
| name | oRPC Disabling Output Validation |
| description | Disable output validation for improved performance while keeping OpenAPI spec generation. |
| license | MIT |
| metadata | {"author":"Ali Torki","homepage":"https://github.com/ali-master","version":"1.0.0"} |
By default, oRPC validates procedure outputs against their defined schemas. If you only define output schemas for OpenAPI specification generation, you can disable output validation to improve performance.
Set initialOutputValidationIndex to NaN:
import { os } from '@orpc/server'
const base = os
.$config({
initialOutputValidationIndex: Number.NaN,
})
All procedures built from base will have output validation disabled.
This approach will not work if your schema transforms data into a different type during validation.
const procedure = base
.output(z.object({ value: z.number().transform(val => String(val)) }))
.handler(() => ({ value: 123 }))
.callable()
const { value } = await procedure()
The client expects value as a string, but since validation is skipped, it receives a number.