Add timezone data to Date
See this proposal: maggiepint/proposal
I have this work well underway.
See maggiepint/proposal-temporal
I am very happy to receive community feedback on this matter, so let me know what you think. I do expect we'll be pushing some updates to the mock API in the next week or so.
Cool... Have some suggestions on tweaks, but looks like a good start... Will look through issues later and as some... At first glance, two things stick out.
Each type should accept a single string input at least in a format that matches the output...
I'd prefer DateTime* over *DateTime, such as DateTimeOffset ... Mainly that indexing in documentation, and Autocomplete will be more discoverable. Even if the sub-type is more intuitive in speach than type
I vote for it. ‘tz’ was already there, but never have been exposed. Same for ‘zlib’ (another topic).
From: Maggie Pint [mailto:maggiepint at gmail.com] Sent: Tuesday, June 20, 2017 7:19 PM To: Michael J. Ryan <tracker1 at gmail.com>
Cc: es-discuss <es-discuss at mozilla.org>
Subject: Re: Add timezone data to Date
I have this work well underway.
See maggiepint/proposal-temporal
I am very happy to receive community feedback on this matter, so let me know what you think. I do expect we'll be pushing some updates to the mock API in the next week or so.
On Tue, Jun 20, 2017 at 4:15 PM, Michael J. Ryan <tracker1 at gmail.com <mailto:tracker1 at gmail.com> > wrote:
Looking at moment-timezone the biggest issue is actually the timezone data.
I'm thinking that if there were a standard representation for browsers and node to make this available it would be a good thing.
I'm suggesting this as a step towards getting moment and/or another better date library into js. Since even with a library the amount of tz data is pretty large and every increasing.
Also, normalizing the zones and current offset and support for dst is a big plus imho. I'm pretty sure this had been discussed before, but have only been liking here a year or so now.
Date parsing is simply unaddressed at this point - it will certainly be there eventually. We are undecided on whether it's a 262 matter or a 402 matter in a lot of cases.
Timezone data is already indirectly accessible via native Intl.DateTimeFormat (I've also once published an util that allows to work that: medikoo/date-from-timezone ).
Still it would be way better if there's some direct access provided, whether it should be directly on Date or on Intl.DateTimeFormat is to be discussed (I would possibly vote for Intl.DateTimeFormat)
-- View this message in context: mozilla.6506.n7.nabble.com/Add-timezone-data-to-Date-tp366272p366292.html Sent from the Mozilla - ECMAScript 4 discussion mailing list archive at Nabble.com.
Looking at moment-timezone the biggest issue is actually the timezone data.
I'm thinking that if there were a standard representation for browsers and node to make this available it would be a good thing.
I'm suggesting this as a step towards getting moment and/or another better date library into js. Since even with a library the amount of tz data is pretty large and every increasing.
Also, normalizing the zones and current offset and support for dst is a big plus imho. I'm pretty sure this had been discussed before, but have only been liking here a year or so now.