"YYYY-mm-dd hh:mm:ss.ssssss" returned by the API is not a valid date
string format for the Date constructor (at least not supported by
Safari). This results in new Date(dateString) returning Invalid Date value in Safari. The value becomes NaN eventually as the lib
process the data and, by default, the string representation for that is
"over a year from now".
The narrowest gap we can close is to make it a supported format by
inserting a "T" where the space between the date and the time is. This
commit does this on the front-end as we render the date but, ideally,
the fix should be applied in the API layer.
"YYYY-mm-dd hh:mm:ss.ssssss" returned by the API is not a valid date string format for the
Dateconstructor (at least not supported by Safari). This results innew Date(dateString)returningInvalid Datevalue in Safari. The value becomesNaNeventually as the lib process the data and, by default, the string representation for that is "over a year from now".The narrowest gap we can close is to make it a supported format by inserting a "T" where the space between the date and the time is. This commit does this on the front-end as we render the date but, ideally, the fix should be applied in the API layer.