Open isaacl opened 3 years ago
This behavior has changed since 1.10.6 in 1.10.6:
> +d("2021-11-18T00:15:00Z").tz('America/New_York')
1637194500000
> +d.tz("2021-11-18T00:15:00Z", "America/New_York")
1637212500000
Hmm OK I was wrong that this was a recent regression. In 1.9.7 however, dayjs.tz does handle isostrings correctly. So I guess this is more of a feature request?
In 1.10.6
In 1.10.7 These are no longer equal.
Expected behavior when parsing a UTC string, d.tz wouldn't interpret the time differently, but rather would just set the timezone after parsing as a UTC time. But now it handles this differently. It is interpreting the string in the context of America/New_York timezone.
Information