-
Notifications
You must be signed in to change notification settings - Fork 64
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
fix: mark the ZodDate
as string
type in the OpenAPI schema
#126
Open
Gamote
wants to merge
1
commit into
BenLorantfy:main
Choose a base branch
from
Gamote:fix/openapi-date-as-string
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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 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 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
Oops, something went wrong.
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.
The implementation should set the 'format' property to 'date-time' for the date type in the OpenAPI schema. Update the code to include 'object.format = "date-time"'.
Copilot is powered by AI, so mistakes are possible. Review output carefully before use.
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.
@BenLorantfy I got this recommendation locally as well, but I wasn't sure that is necessary. Let me know.
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.
@Gamote I don't think it's a bad idea, but it should probably be
date
, notdate-time
: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.
@BenLorantfy In that case it might be a bit more common that people are sharing ISO strings rather than just the date. What is your take on it?
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.
We might need to support both
format: "date"
andformat: "date-time"
. But we need a way to tell them apart (e.g. is this zod schema az.string().date()
schema or az.string().datetime()
schema). I can look into that later tonight or tmr if we're unsure how to do so.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.
Yeah it might be the best approach, I can try to look into it tomorrow too, but I do agree that supporting both might be the way to go.
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.
Hello, if it helps, I see you can check the format of a string with isDate or isDateTime.
You can do this when you know that the schema is a string
Edit: Sorry, the library already handles the string type with date and dateTime.
If it can helps my use case of z.date is to add a transform the date object to a specific format.
This is used in a serializer.
z.date().transform(serializeDate)
In this case, you cannot guess the format
You will have a ZodEffect, the zodEffect schema contains a z.Date and not a z.String.
To conclude : The recommendation is good, z.Date will be transformed in string and it is always a datetime.