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
Hello, I found out this strange behaviour when creating TZDate on the day of DST transition in Prague - that is on 27.10.2024, from GMT+2 to GMT+1. The target zone is always Europe/Prague, but when I am in a Pacific time zone, there is a certain bug.
// the following examples are in Pacific Time local timezone // this results in "Sun Oct 27 2024 01:00:00 GMT+0200" instead of "00:00:00" and it seems shifted because the day actually has 25 hoursnewTZDate(2024,9,27,0,'Europe/Prague').toString()// in other dates, the result is fine, in this case "Sat Oct 26 2024 00:00:00 GMT+0200"newTZDate(2024,9,26,0,'Europe/Prague').toString()// now the following example is in Europe/Prague local timezone// this correctly returns "Sun Oct 27 2024 00:00:00 GMT+0200"newTZDate(2024,9,27,0,'Europe/Prague').toString()
In order to get 00:00:00 from the Pacific Time local timezone, I have to use hour index of -1, which shouldn't be the case I believe.
The text was updated successfully, but these errors were encountered:
This seems to be fixed in version 1.1.1 thanks to the related issue #11 , I was actually testing on 1.0.2 and did not realize it has been fixed, so this issue can probably be closed :).
Hello, I found out this strange behaviour when creating TZDate on the day of DST transition in Prague - that is on 27.10.2024, from GMT+2 to GMT+1. The target zone is always Europe/Prague, but when I am in a Pacific time zone, there is a certain bug.
In order to get 00:00:00 from the Pacific Time local timezone, I have to use hour index of -1, which shouldn't be the case I believe.
The text was updated successfully, but these errors were encountered: