Converting an timezoned instance to another timezone returns the wrong result #1305
Comments
|
Seems to work properly in |
|
bug confirmed, will fix soon |
iamkun
added a commit
that referenced
this issue
Jan 4, 2021
iamkun
added a commit
that referenced
this issue
Jan 4, 2021
iamkun
added a commit
that referenced
this issue
Jan 4, 2021
iamkun
pushed a commit
that referenced
this issue
Jan 5, 2021
## [1.10.2](v1.10.1...v1.10.2) (2021-01-05) ### Bug Fixes * fix parse regex bug ([#1307](#1307)) ([db2b6a5](db2b6a5)), closes [#1305](#1305) * remove module entry in package.json to revert 1.10.1 change ([#1314](#1314)) ([824dcb8](824dcb8)) * update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](#1315)) ([b0dda31](b0dda31))
|
🎉 This issue has been resolved in version 1.10.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Mar 16, 2021
andrewhood125ruhuc
added a commit
to andrewhood125ruhuc/SidRH2
that referenced
this issue
May 10, 2022
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05) ### Bug Fixes * fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([db2b6a5](iamkun/dayjs@db2b6a5)), closes [#1305](iamkun/dayjs#1305) * remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([824dcb8](iamkun/dayjs@824dcb8)) * update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([b0dda31](iamkun/dayjs@b0dda31))
andrewhood125ruhuc
added a commit
to andrewhood125ruhuc/SidRH2
that referenced
this issue
May 10, 2022
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05) ### Bug Fixes * fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([db2b6a5](iamkun/dayjs@db2b6a5)), closes [#1305](iamkun/dayjs#1305) * remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([824dcb8](iamkun/dayjs@824dcb8)) * update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([b0dda31](iamkun/dayjs@b0dda31))
allmoviestvshowslistsfilmography28
added a commit
to allmoviestvshowslistsfilmography28/dayjs
that referenced
this issue
Sep 12, 2024
## [1.10.2](iamkun/dayjs@v1.10.1...v1.10.2) (2021-01-05) ### Bug Fixes * fix parse regex bug ([#1307](iamkun/dayjs#1307)) ([082a55a](iamkun/dayjs@082a55a)), closes [#1305](iamkun/dayjs#1305) * remove module entry in package.json to revert 1.10.1 change ([#1314](iamkun/dayjs#1314)) ([648899c](iamkun/dayjs@648899c)) * update devHelper add warning "passing Year as a Number will be parsed as a Unix timestamp" ([#1315](iamkun/dayjs#1315)) ([a4480c1](iamkun/dayjs@a4480c1))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I am trying to convert a time that I parsed using
dayjs.tzinto another timezone, but it appears to return the incorrect value.This appears to be a regression, as it appears to work properly in
1.9.7, though I'm not sure when this issue started.In
1.9.7(working properly): https://codepen.io/pikachews/pen/ZEpxwGEIn
1.10.1(working incorrectly): https://codepen.io/pikachews/pen/NWRYoGoExpected behavior
It should properly convert and return the correct time.
Information
The text was updated successfully, but these errors were encountered: