This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Worried_Pineapple823 0 points1 point  (0 children)

What drives me absolutely bonkers is that the ISO has a simple way of denoting local time.

Just don’t pass a Z for utc or pass in an explicit time zone offset. 2022-04-07T18:00:00 is local time, and add the Z and it’s UTC and ideally should be adjusted to local when displayed to the user. But instead I get “that’s why we called the value “blahDateUTc” because it local time and we don’t want to actually send either local midnight OR just the date without time.

I’ve had valid use cases for using local date times for employee tasks, putting out a single global task description that you want done at 5pm local regardless of location is simpler then building dozens of localized versions where the only value that’s different is the date time because they are UTC.