flux-pr-5187
Zod (TypeScript) · W2 · GPT-5.1 Codex Mini
Tests failed. 0/1 commands passed. Strength: weak.
npx vitest run packages/zod/src/v4/core/tests/locales/es.test.ts -t "Spanish\ locale\ \-\ type\ name\ translations\ in\ too_small\ errors|Spanish\ locale\ \-\ type\ name\ translations\ in\ too_big\ errors|Spanish\ locale\ \-\ type\ name\ translations\ in\ invalid_type\ errors|Spanish\ locale\ \-\ fallback\ for\ unknown\ type\ names|Spanish\ locale\ \-\ other\ error\ cases"Partial score: 0/1
Trajectory
unknown · partial order onlyCanonical trajectory missing; showing coarse derived order only.
Quality
Equivalence Reasoning
behavioral
The patch applies type-name translation in the right error branches, but the Spanish type map is incomplete (e.g., missing `enum`, `union`, `literal`, `void`, `never`, `unknown`, `any`, etc.), so some expected/received labels can still appear as raw English type names. It also changes translation choices (e.g., `string -> cadena`) that may diverge from the intended locale outputs.
Code Review
The patch moves in the right direction and touches the required error codes, but it likely does not fully satisfy the intended change because type-name localization is not comprehensive and some translated terms appear mismatched to expected outputs.
The new `TypeNames` map omits labels like `enum`, `union`, `literal`, `void`, `never`, `unknown`, and `any`, so `invalid_type`/origin-based messages can still emit raw English for known types instead of consistent Spanish translations.
The patch uses alternate wording (`string` -> `cadena`, `bigint` -> `entero grande`) rather than the expected locale vocabulary, which is likely to fail message-level tests tied to exact Spanish phrasing.