fix(typescript-zod): validate date and time formats - #3505
Conversation
cb5dca6 to
8ea1d93
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
8ea1d93 to
8f1a07a
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
242473b to
b46e83d
Compare
8f1a07a to
026db92
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
7876d0b to
a8cf6b3
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
a8cf6b3 to
2399eed
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
2399eed to
d328bcc
Compare
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
|
This shouldn't repeat the whole long zod codec for every single instance in the file. Instead, if the codec is needed, it should be defined once and then used. |
d328bcc to
31267ac
Compare
|
Fixed in 31267ac. Each required codec is now emitted once and reused; unused codecs are omitted. The emission unit covers single definitions, multiple references, and absence. |
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
Generated-output differences67 files differ — 67 modified, 0 new, 0 deleted |
1 participant
Zod emitted plain strings for JSON Schema
dateandtime, while its coercing date-time schema accepted invalid values. Validate calendar dates, time ranges, and date-time shape before conversion.Each required codec is emitted once and reused. Unused codecs are omitted from generated output.
Introduces shared invalid date/time cases 5 and 6. The 26-production-line exception was explicitly approved.
Validation: build; lint; TypeScript Zod fixtures 145/145.