You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apologies if this has been brought up. I've searched through the issues and found some that are related, but don't report this exactly. I have the following:
I have a Milestones schema/list with a field called due_date that is required. I am attempting to set a full-date string as the default value like the docs recommended:
Error: The calendarDay field at Milestone.due_date specifies defaultValue: 1970-01-01T00:00:00.00Z but values must be provided as a full-date ISO8601 string such as 1970-01-01
Please describe what you expected to happen
calendarDay() field should accept ISO8601 full-date string format as a default value
Please add contextual information such as your node version (node -v), or the web browser you used
Workaround would be to add some kind of setting to calendarDay to not use native database types for postgresql and mysql. Error does not happen for sqlite because it uses String in this case.
Steps to reproduce
My apologies if this has been brought up. I've searched through the issues and found some that are related, but don't report this exactly. I have the following:
I have a
Milestones
schema/list with a field calleddue_date
that is required. I am attempting to set a full-date string as the default value like the docs recommended:However, when I run
keystone prisma migrate dev
this produces the following error:So I attempted to adjust the value to fit rfc3339 date-time format:
I then receive the following error:
Please describe what you expected to happen
calendarDay()
field should accept ISO8601 full-date string format as a default valuePlease add contextual information such as your node version (node -v), or the web browser you used
The text was updated successfully, but these errors were encountered: