-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider a replacement for moment-timezone-with-data-1970-2030.js
#1110
Comments
You're right, this is going to be a problem. We've seen a lot of issues when deprecating/removing the old hard-coded 10-year files ( I like your idea of basing the end date on a rolling |
This isn't urgent yet, but the year 2030 is approaching, so rather sooner than later something should be done about the file
moment-timezone-with-data-1970-2030.js
.After the year 2030 it will no longer be useful for current dates, so that is a definite deadline. But as the data is also used for future dates, this will be an issue even earlier. If you want to handle dates up to 5 years into the future (like the file
moment-timezone-with-data-10-year-range.js
allows), then something should be done within the next year.Possible alternatives are:
moment-timezone-with-data-1970-2040.js
file, and discuss the matter again in 10 years (if this library lives that long).currentYear + 5
(likemoment-timezone-with-data-10-year-range.js
), or evencurrentYear + 10
(if users ofmoment-timezone-with-data-1970-2030.js
expect it to go further into the future).The text was updated successfully, but these errors were encountered: