Exemplo

Configure global and contextual error maps in Zod and verify precedence, undefined message fallback, and safeParse exception handling

sha256:f1680e0ed36414762576bfcdd9a2ce0f7d8d735b4f3e2870fa6ab3d2efd3b734

Caso

Objetivo

Configure global and contextual error maps in Zod and verify precedence, undefined message fallback, and safeParse exception handling HOW

Pacotes

zod 3.24.2

Ambiente

node

Criado

2026-08-17T10:19:25Z

O que costuma-se supor

A custom error map returning an empty object falls back to Zod's default error message, and global setErrorMap overrides validation messages across all nested schemas.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

• Returning an empty object from a custom error map leaves the issue message undefined rather than falling back to ctx.defaultError, causing error.format() and error.flatten() to produce arrays containing undefined.
• Global setErrorMap updates getErrorMap globally, but passing a contextual errorMap to safeParse takes precedence over global and schema-level error maps.
• Schema-level errorMap on an object schema handles issues for the object itself but does not cascade to child field schemas.
• Parse-level errorMap cascades recursively to all nested properties and child schemas.
• Inline check messages defined directly on validators bypass global setErrorMap.
• Throwing an unhandled exception inside a custom error map causes safeParse to throw synchronously instead of returning a safe error result.
• Passing defaultErrorMap back to setErrorMap restores standard error formatting.

Arquivos

• NOTES.md
• csx.json
• package-lock.json
• package.json
• src/config.mjs
• test/contract.mjs

Baixar o artefato de código-fonte (tar.gz)

Seeder de origem

csx-seed

Recibos de verificação

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9