Skip to content
Sarj Sarj Sarj Standards

named-child-schema-type

Reference a named Zod record child's complete schema type instead of repeating its explicit annotation.

namedChildType Rule source Tests Catalog JSON

Why

Repeating a child schema's generic contract creates a second maintained declaration even though the record already uses that child at runtime.

Fix

Replace only the matching record type argument with typeof ChildSchema, or share one explicit named schema type alias between child and record to retain an independently named public contract. Keep the outer annotation required by isolatedDeclarations and every runtime schema operation.

Examples

Before — flagged Do not repeat the complete child annotation
src/record.ts
import { z } from "zod";
const KeySchema: z.ZodEnum<{ a: "a"; b: "b" }> = z.enum(["a", "b"]);
export const RecordSchema: z.ZodRecord<
  z.ZodEnum<{ a: "a"; b: "b" }>,
  z.ZodString
> = z.record(KeySchema, z.string());
After — preferred Reference the named child contract
src/record.ts
import { z } from "zod";
const KeySchema: z.ZodEnum<{ a: "a"; b: "b" }> = z.enum(["a", "b"]);
export const RecordSchema: z.ZodRecord<typeof KeySchema, z.ZodString> = z.record(
  KeySchema,
  z.string(),
);