Skip to content

Conversation

@kossnocorp
Copy link
Member

@kossnocorp kossnocorp commented Dec 7, 2018

Rework approach to DST handling to make it more bulletproof.

To do:

Remove code that causes #972. Most likely it will break something else,
but this is yet to figure.
@kossnocorp kossnocorp changed the title Fix DST issue (closes #972) Fix DST issue (closes #972, closes #992) Dec 7, 2018
@kossnocorp kossnocorp merged commit efdbf3b into master Dec 10, 2018
@kossnocorp kossnocorp deleted the 972-dst-bug branch December 10, 2018 07:52
kossnocorp added a commit that referenced this pull request Dec 10, 2018
kossnocorp added a commit that referenced this pull request Dec 10, 2018
kossnocorp added a commit that referenced this pull request Dec 10, 2018
@kronthto
Copy link

kronthto commented Oct 26, 2019

I think taking the next day into consideration causes weird behaviour in some cases. See:

// import dateformat from 'date-fns/format'

> dateformat('2019-10-26T22:40:00')
"2019-10-26T23:40:00.000+02:00"

(format calling parse)
It makes 23:40 out of 22:40.

date-fns version: 1.30.1 - this change was backported there.

This is with a Europe/Berlin Browser/system timezone, we have DST change at 2019-10-27 03:00 (the day after that date).

Sorry if this was already reported/fixed elsewhere, or I'm wrong / this is intended. Tbh. I didn't put too much effort into tracking it down further but it lead me here and I wanted to report it.

Yep I see there is already #1500 so ignore this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants