fix(types): Accept datetime with microsecond precision and timezone offsets#115
Merged
dcramer merged 5 commits intodcramer:mainfrom Feb 17, 2026
Merged
fix(types): Accept datetime with microsecond precision and timezone offsets#115dcramer merged 5 commits intodcramer:mainfrom
dcramer merged 5 commits intodcramer:mainfrom
Conversation
…ffsets Python and other tools that agents may use emit timestamps with higher precision than JavaScript's native Date.toISOString(). Update the datetime schema to accept variable fractional seconds and timezone offsets.
|
@unexge is attempting to deploy a commit to the David Cramer's projects Team on Vercel. A member of the Team first needs to authorize it. |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Owner
|
sorry im slow af here - i think i either lost these notifications in the 100s that come in from sentry, or i am just not getting them on this repo |
Zod's datetime() already accepts variable fractional seconds by default;
the { offset: true } option only adds timezone offset support.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I started getting errors like:
in one of my projects, and
completed_atwas2026-02-05T08:56:48.487608+00:00. Not sure if Dex created this datetime originally or if my agent skip Dex and edited JSONL directly (which is more likely) but I feel like it would be beneficial to make datetime parser more liberal.