Open djbusby opened 1 year ago
Also noticed on upload Area_XX_20221101T151854519.csv
the error response file was Area_XX_20221101T151927.csv
-- missing the microseconds.
LCB Incident Report: IR65290
ALso, rleated this one is missing the leading zero on the month Manifest_AF0E72B77C_01GPES556DMBZ1YQRCQWG3QZ4F_2023111T822904.csv
So, it makes parsing the time information wrong; cause when the leading zero is missing, is it missing from the month or the day? Same on the time for hour/minute second -- like when the milliseconds are missing.
I mean, time formatting is trivial and folks have been telling your agency about ISO8601 and RFC3339 for at least five years.
Related to https://github.com/openthc/ccrs/issues/69
The documentation states that the CSVs will have a datetime format matching
Ymd\TGisv
(from PHP DateTime->format(). However sometimes we see a response that is onlyYmd\TGis
which is unexpected.Expect:
Inventory_XX_20221101T143621952.csv
Actual:Inventory_XX_20221101T143615.csv
Most files include the microseconds; but sometimes it seems it gets dropped?