Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
parseISO returning wrong time on day of offset change
See original GitHub issueIn Germany the offset will change from +1 to +2 on March 29th. When using parseISO on a timestamp on this day the result is one hour off:
parseISO('2020-03-28T10:00:00') // Sat Mar 28 2020 10:00:00 GMT+0100
parseISO('2020-03-29T10:00:00') // Sun Mar 29 2020 11:00:00 GMT+0200
parseISO('2020-03-30T10:00:00') // Mon Mar 30 2020 10:00:00 GMT+0200
This happens on version 2.9.0
Anyone else ran into the same problem and has a potential fix for this?
EDIT: Just wanted to add that this happens on Chrome, Firefox and Edge Chromium
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
just tried with the latest version 2.10.0. same result. returned dates are off by one hour
I created pr with a fix, but it uses completely another approach, anyone concerned please test it.