-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(schema-to-json): support serializing Zod 4 z.date() to JSON Schema #4962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
kaiizer777
wants to merge
1
commit into
triggerdotdev:main
from
kaiizer777:fix/zod4-date-json-schema
+58
−0
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@trigger.dev/schema-to-json": patch | ||
| --- | ||
|
|
||
| Support serializing Zod 4 `z.date()` schemas to JSON Schema format. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Older Zod versions weaken schemas
With Zod 4.0–4.4, the
unrepresentablefunction disables throwing for non-date types. Those releases only compare the option with"throw", so unsupported schemas become{}and accept rejected values.Learn more
The package accepts Zod
^4.0.0, but function-valuedunrepresentablehandlers were added only in later Zod 4 releases. Earlier releases treat every value except the literal"throw"as permissive behavior. The callback therefore never runs there, although the existingoverridestill converts dates. Other unrepresentable nodes lose their previous errors and emit unconstrained schemas.Example: With Zod 4.1, converting
z.symbol()previously throws. After this change it emits{}, which permits strings and numbers even thoughz.symbol()rejects them.Recommended fix: Either raise both Zod dependency ranges to the first version supporting
UnrepresentableHandler, or preserve compatibility by detecting that capability and explicitly throwing fromoverridefor every non-date unrepresentable node on older releases. Add a test installed against the minimum supported Zod 4 version.Was this helpful? React with 👍 or 👎 to provide feedback.