fix #2598

Summary

⚠️ BREAKING CHANGE: Unified Zod schema naming convention to PascalCase

Changed all Zod schema exports to PascalCase to align with TypeScript type definition naming conventions.

Purpose

Orval is currently being improved to output both Zod schemas and TypeScript type definitions. By including both in a single .zod.ts file, schemas and types can be handled with the same name.

// createPetsBody.zod.ts
export const CreatePetsBody = zod.object({
  name: zod.string(),
  tag: zod.string()
})

export type CreatePetsBody = zod.infer<typeof CreatePetsBody>

import { CreatePetsBody } from './createPetsBody.zod'

// Use as type
const body: CreatePetsBody = { name: 'Fluffy', tag: 'cat' }

// Use as schema (runtime validation)
CreatePetsBody.parse(body)

Since TypeScript type definitions use PascalCase as standard, Zod schemas need to follow the same naming convention. This allows schemas and types to be handled with the same name, improving developer experience.

Changes

- export const createPetsBody = zod.object({
+ export const CreatePetsBody = zod.object({
    name: zod.string(),
    tag: zod.string()
  })

- export type CreatePetsBody = zod.infer<typeof createPetsBody>
+ export type CreatePetsBody = zod.infer<typeof CreatePetsBody>

Migration Guide

If your existing code imports Zod schemas, change the import names to PascalCase:

- import { createPetsBody } from './api'
+ import { CreatePetsBody } from './api'