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
suggest that the typia.tags.Format > "date-time" | "date" | "time" format follow RFC3339.
Problem
The current typia.tags.Format<'date-time'> format follows just ISO8601. it allows time and timezone to be omitted. And the type is represented as date-time in swagger when building swagger documentation.
However, the date-time format in swagger is defined by the date-time format in the RFC3339 standard, which requires the time and timezone to be indicated.
In conclusion, the current typia definition of date-time leads to inaccuracies in documentation and confusion of terms.
Therefore, I suggest the following
Suggest
format
RFC3339 standard full-date format is define typia.tags.Format<'date'>
RFC3339 standard full-time format is define typia.tags.Format<'time'>
RFC3339 standard date-time format is define typia.tags.Format<'date-time'>
Summary
suggest that the
typia.tags.Format > "date-time" | "date" | "time"
format followRFC3339
.Problem
The current
typia.tags.Format<'date-time'>
format follows just ISO8601. it allows time and timezone to be omitted. And the type is represented asdate-time
in swagger when building swagger documentation.However, the
date-time
format in swagger is defined by thedate-time
format in theRFC3339
standard, which requires the time and timezone to be indicated.In conclusion, the current typia definition of
date-time
leads to inaccuracies in documentation and confusion of terms.Therefore, I suggest the following
Suggest
format
RFC3339
standardfull-date
format is definetypia.tags.Format<'date'>
RFC3339
standardfull-time
format is definetypia.tags.Format<'time'>
RFC3339
standarddate-time
format is definetypia.tags.Format<'date-time'>
code
Example
Reference
The text was updated successfully, but these errors were encountered: