Add timezone data to Date

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Add timezone data to Date

Michael J. Ryan
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.

--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Add timezone data to Date

Jordan Harband

On Tue, Jun 20, 2017 at 4:15 PM, Michael J. Ryan <[hidden email]> 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.

--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss



_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Add timezone data to Date

Maggie Pint
In reply to this post by Michael J. Ryan
I have this work well underway.


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 <[hidden email]> 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.

--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss



_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Add timezone data to Date

Michael J. Ryan
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-sub


--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

On Jun 20, 2017 4:18 PM, "Maggie Pint" <[hidden email]> wrote:
I have this work well underway.


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 <[hidden email]> 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.

--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss



_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

RE: Add timezone data to Date

doodad-js Admin
In reply to this post by Maggie Pint

I vote for it. ‘tz’ was already there, but never have been exposed. Same for ‘zlib’ (another topic).

 

From: Maggie Pint [mailto:[hidden email]]
Sent: Tuesday, June 20, 2017 7:19 PM
To: Michael J. Ryan <[hidden email]>
Cc: es-discuss <[hidden email]>
Subject: Re: Add timezone data to Date

 

I have this work well underway.

 

 

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 <[hidden email]> 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.


--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.


_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss

 


_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Add timezone data to Date

Maggie Pint
In reply to this post by Michael J. Ryan
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.

On Tue, Jun 20, 2017 at 4:30 PM, Michael J. Ryan <[hidden email]> wrote:
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-sub


--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

On Jun 20, 2017 4:18 PM, "Maggie Pint" <[hidden email]> wrote:
I have this work well underway.


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 <[hidden email]> 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.

--
Michael J. Ryan - [hidden email] - http://tracker1.info

Please excuse grammar errors and typos, as this message was sent from my phone.

_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss




_______________________________________________
es-discuss mailing list
[hidden email]
https://mail.mozilla.org/listinfo/es-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Add timezone data to Date

medikoo
In reply to this post by Michael J. Ryan
Timezone data is already *indirectly* accessible via native Intl.DateTimeFormat (I've also once published an util that allows to work that: https://github.com/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)