-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
add timezone support #4843
add timezone support #4843
Conversation
Would be nice to have this merged! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't let me comment on the file, but it looks like Chart.js is now a submodule of itself. :|
required fix has been applied |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am ok with the functionality. @benmccann @simonbrunel are you ok with this and bringing in a new dependency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
Sorry I'm taking awhile to review this. I want to give it really deep thought and do plan to take a look |
@touletan I really appreciate the hard word you've put into this PR. I've been spending a lot of time digging into this during the past week trying to ensure we take the best path forward. My main concern is that we already get a lot of complaints about how big I reached out to one of the maintainers of moment after coming across their blog while researching possible paths forward and they suggested we might want to consider the new Moment project Luxon: http://moment.github.io/luxon/. The issue with switching to Luxon is that it is not backwards-compatible. If possible, it would be nice if we didn't leak our usage Moment into our APIs, so that we could make internal changes that users need not be aware of. However, given the situation we are into today I think perhaps this might have to wait until 3.0.0. Thoughts @etimberg @simonbrunel ? |
I'm OK with trying out moving to Luxon. Not sure if we want the next version to be 3.0 or not. @simonbrunel what are your thoughts? |
Closing due to inactivity |
I've created issue #5186 to consolidate the various pieces of feedback we've received regarding time zone support. Please feel free to subscribe to it for updates |
Add moment-timezone module to support timezone in time scale
proposed solution to fix this:
Timezone support
Codepen Example