Add timezone data to Date
Michael J. Ryan
tracker1 at gmail.com
Tue Jun 20 23:30:30 UTC 2017
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
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
Michael J. Ryan - tracker1 at gmail.com - http://tracker1.info
Please excuse grammar errors and typos, as this message was sent from my
On Jun 20, 2017 4:18 PM, "Maggie Pint" <maggiepint at gmail.com> wrote:
> I have this work well underway.
> See https://github.com/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>
>> Looking at moment-timezone the biggest issue is actually the timezone
>> 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.
>> Michael J. Ryan - tracker1 at gmail.com - http://tracker1.info
>> Please excuse grammar errors and typos, as this message was sent from my
>> es-discuss mailing list
>> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss