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
For instance, release 2e6374f8-420b-353b-8c42-dbb249bfac1c's date is simply "1984" without the month and day. When retrieved with this crate, it is converted to a NaiveDate with value "1984-01-01", supposedly due to this logic. Doesn't seem to have a way to restore the original "1984" value.
Sure, we can heuristically say if the date's month and day are both 1, most likely they can be discarded. But there could be case where the release date is really on the new year's day.
Maybe instead of deserialize the date to a NaiveDate, simply keep it as String, and let user choose which library to use?
The text was updated successfully, but these errors were encountered:
For instance, release 2e6374f8-420b-353b-8c42-dbb249bfac1c's date is simply "1984" without the month and day. When retrieved with this crate, it is converted to a
NaiveDate
with value "1984-01-01", supposedly due to this logic. Doesn't seem to have a way to restore the original "1984" value.Sure, we can heuristically say if the date's month and day are both 1, most likely they can be discarded. But there could be case where the release date is really on the new year's day.
Maybe instead of deserialize the date to a
NaiveDate
, simply keep it asString
, and let user choose which library to use?The text was updated successfully, but these errors were encountered: