The bug I'm reporting is that the times we display in the API do not have a time zone associated with them.
If we called isotime on the times from the db, we would get them marked with a default UTC (Z) time zone, which is what should happen, since they're UTC times internally.
The bug I'm reporting is that the times we display in the API do not have a time zone associated with them.
If we called isotime on the times from the db, we would get them marked with a default UTC (Z) time zone, which is what should happen, since they're UTC times internally.
Cory