Skip to content

Instantly share code, notes, and snippets.

@jaens
Last active May 1, 2026 18:20
Show Gist options
  • Select an option

  • Save jaens/7e15ae1984bb338c86eb5e452dee3010 to your computer and use it in GitHub Desktop.

Select an option

Save jaens/7e15ae1984bb338c86eb5e452dee3010 to your computer and use it in GitHub Desktop.
Zod deep strict and `deepPartial` utility
/*
Copyright 2024, Jaen - https://github.com/jaens
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/
import { z, type ZodDiscriminatedUnionOption } from "zod";
const RESOLVING = Symbol("mapOnSchema/resolving");
export function mapOnSchema<T extends z.ZodTypeAny, TResult extends z.ZodTypeAny>(
schema: T,
fn: (schema: z.ZodTypeAny) => TResult,
): TResult;
/**
* Applies {@link fn} to each element of the schema recursively, replacing every schema with its return value.
* The rewriting is applied bottom-up (ie. {@link fn} will get called on "children" first).
*/
export function mapOnSchema(schema: z.ZodTypeAny, fn: (schema: z.ZodTypeAny) => z.ZodTypeAny): z.ZodTypeAny {
// Cache results to support recursive schemas
const results = new Map<z.ZodTypeAny, z.ZodTypeAny | typeof RESOLVING>();
function mapElement(s: z.ZodTypeAny) {
const value = results.get(s);
if (value === RESOLVING) {
throw new Error("Recursive schema access detected");
} else if (value !== undefined) {
return value;
}
results.set(s, RESOLVING);
const result = mapOnSchema(s, fn);
results.set(s, result);
return result;
}
function mapInner() {
if (schema instanceof z.ZodObject) {
const newShape: Record<string, z.ZodTypeAny> = {};
for (const [key, value] of Object.entries(schema.shape)) {
newShape[key] = mapElement(value as z.ZodTypeAny);
}
return new z.ZodObject({
...schema._def,
shape: () => newShape,
});
} else if (schema instanceof z.ZodArray) {
return new z.ZodArray({
...schema._def,
type: mapElement(schema._def.type),
});
} else if (schema instanceof z.ZodMap) {
return new z.ZodMap({
...schema._def,
keyType: mapElement(schema._def.keyType),
valueType: mapElement(schema._def.valueType),
});
} else if (schema instanceof z.ZodSet) {
return new z.ZodSet({
...schema._def,
valueType: mapElement(schema._def.valueType),
});
} else if (schema instanceof z.ZodOptional) {
return new z.ZodOptional({
...schema._def,
innerType: mapElement(schema._def.innerType),
});
} else if (schema instanceof z.ZodNullable) {
return new z.ZodNullable({
...schema._def,
innerType: mapElement(schema._def.innerType),
});
} else if (schema instanceof z.ZodDefault) {
return new z.ZodDefault({
...schema._def,
innerType: mapElement(schema._def.innerType),
});
} else if (schema instanceof z.ZodReadonly) {
return new z.ZodReadonly({
...schema._def,
innerType: mapElement(schema._def.innerType),
});
} else if (schema instanceof z.ZodLazy) {
return new z.ZodLazy({
...schema._def,
// NB: This leaks `fn` into the schema, but there is no other way to support recursive schemas
getter: () => mapElement(schema._def.getter()),
});
} else if (schema instanceof z.ZodBranded) {
return new z.ZodBranded({
...schema._def,
type: mapElement(schema._def.type),
});
} else if (schema instanceof z.ZodEffects) {
return new z.ZodEffects({
...schema._def,
schema: mapElement(schema._def.schema),
});
} else if (schema instanceof z.ZodFunction) {
return new z.ZodFunction({
...schema._def,
args: schema._def.args.map((arg: z.ZodTypeAny) => mapElement(arg)),
returns: mapElement(schema._def.returns),
});
} else if (schema instanceof z.ZodPromise) {
return new z.ZodPromise({
...schema._def,
type: mapElement(schema._def.type),
});
} else if (schema instanceof z.ZodCatch) {
return new z.ZodCatch({
...schema._def,
innerType: mapElement(schema._def.innerType),
});
} else if (schema instanceof z.ZodTuple) {
return new z.ZodTuple({
...schema._def,
items: schema._def.items.map((item: z.ZodTypeAny) => mapElement(item)),
rest: schema._def.rest && mapElement(schema._def.rest),
});
} else if (schema instanceof z.ZodDiscriminatedUnion) {
const optionsMap = new Map(
[...schema.optionsMap.entries()].map(([k, v]) => [
k,
mapElement(v) as ZodDiscriminatedUnionOption<string>,
]),
);
return new z.ZodDiscriminatedUnion({
...schema._def,
options: [...optionsMap.values()],
optionsMap: optionsMap,
});
} else if (schema instanceof z.ZodUnion) {
return new z.ZodUnion({
...schema._def,
options: schema._def.options.map((option: z.ZodTypeAny) => mapElement(option)),
});
} else if (schema instanceof z.ZodIntersection) {
return new z.ZodIntersection({
...schema._def,
right: mapElement(schema._def.right),
left: mapElement(schema._def.left),
});
} else if (schema instanceof z.ZodRecord) {
return new z.ZodRecord({
...schema._def,
keyType: mapElement(schema._def.keyType),
valueType: mapElement(schema._def.valueType),
});
} else {
return schema;
}
}
return fn(mapInner());
}
export function deepPartial<T extends z.ZodTypeAny>(schema: T): T {
return mapOnSchema(schema, (s) => (s instanceof z.ZodObject ? s.partial() : s)) as T;
}
/** Make all object schemas "strict" (ie. fail on unknown keys), except if they are marked as `.passthrough()` */
export function deepStrict<T extends z.ZodTypeAny>(schema: T): T {
return mapOnSchema(schema, (s) =>
s instanceof z.ZodObject && s._def.unknownKeys !== "passthrough" ? s.strict() : s,
) as T;
}
export function deepStrictAll<T extends z.ZodTypeAny>(schema: T): T {
return mapOnSchema(schema, (s) => (s instanceof z.ZodObject ? s.strict() : s)) as T;
}
@ahrjarrett

ahrjarrett commented Aug 6, 2025

Copy link
Copy Markdown

Also I've been experimenting with different ways of introducing recursion schemes to a broader TypeScript audience.

My first attempt at making them more accessible was a blogpost, but I'm not happy with it, maybe you'll have some ideas.

I know @josephjunker has written about them before. Recently we've discussed possibly working on something together. If you're interested in collaborating, the more the merrier I'm sure :)

@jaens

jaens commented Aug 6, 2025

Copy link
Copy Markdown
Author

@ahrjarrett Hah ya crazy lad, looks like you did it... I off-handedly mentioned Functors in my comments, although I did have F-algebras and HKT emulation etc. in the back of my mind, the margin wasn't big enough to write that note ;)

I think transforming Zod (or schemas in general) is probably the closest one would get to recursion schemes and all that jazz in "everyday" TypeScript programming (...very likely outnumbering people eg. implementing programming languages or DSLs). You kind of have to have a "wide" recursive sum type (like a Zod schema) to actually feel the need for it, otherwise just "bruteforcing" (ie. inlining) the recursion for every transformer is the "obvious" option.

(general thoughts follow)

Another theoretical concept that I feel is underutilized in TS is lenses... every time I work on a complicated form in React I just facepalm at the fragile boilerplate required to keep everything coherent manually.

I think the current TS FP libraries suffer a bit from trying to be the "one true way", having absolutely every FP abstraction under the sun, so for someone starting out the eyes glaze over...

...and as much as I appreciate FP abstractions for their clarity in guiding thought and generally "railroading" you into reliable and complete solutions, eg. I would never use a standard/trivial Result<> type in production programming, as the debugging and other "real engineering" properties of it are [censored]. (take a dive into the world of Rust advanced error handling crates to see the minimum what of I would consider an acceptable solution over exceptions)


and yeah, I certainly have wanted for these ideas to reach a larger audience...

@ahrjarrett

ahrjarrett commented Aug 8, 2025

Copy link
Copy Markdown

Another theoretical concept that I feel is underutilized in TS is lenses... every time I work on a complicated form in React I just facepalm at the fragile boilerplate required to keep everything coherent manually.

Couldn't agree more. You might be interested zx.makeLens, which is something I've been meaning to get back to working on. Users can pass a zod schema and a "selector" function (which is a just a Proxy that tracks property access) to get back a lens, prism or traversal (depending on what they selected).

Under the hood, the implementation uses the Profunctor encoding, but I've also been meaning to try out the existential encoding.

Support is still experimental, it's mostly just a POC for now.

@dokson

dokson commented May 1, 2026

Copy link
Copy Markdown

Hi @jaens — porting your mapOnSchema pattern to Zod v4 in colinhacks/zod#5928 (closes #2854).

The traversal pattern (bottom-up rewrite + RESOLVING sentinel for cycle detection) is yours; the v4 port dispatches on schema._zod.def.type instead of instanceof (so user-defined schema types pass through without silent breakage), constructs new schemas via core.clone instead of new ZodFoo(...), and covers the v4 def vocabulary (object, array, tuple+rest, record, map, set, union, intersection, optional/nullable/default/prefault/nonoptional/catch/readonly/promise/success, pipe, function, lazy). Apache-2.0 attribution preserved at the top of core/map-on-schema.ts.

deepPartial is built on it; discriminated unions degrade to plain union over the partialed options (since making the discriminator optional collapses the fast-path lookup into duplicate undefined entries — documented in a test).

Would value your review of the v4 port if you have a few minutes — especially whether the cycle handling matches what you intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment