You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 15, 2023. It is now read-only.
Currently, moment-timezone doesn't work properly on frozen moments because its updateOffset implementation assumes that it is using the mutable API.
In moment/moment-rfcs#2, I proposed automatically thawing the moment before updateOffset and then re-freezing afterward (or copying the changed properties when updateOffset is called during the constructor). I'm not sure how a plugin would get access to do that, but I'll leave this issue open in case other folks have better ideas.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, moment-timezone doesn't work properly on frozen moments because its
updateOffset
implementation assumes that it is using the mutable API.In moment/moment-rfcs#2, I proposed automatically thawing the moment before updateOffset and then re-freezing afterward (or copying the changed properties when updateOffset is called during the constructor). I'm not sure how a plugin would get access to do that, but I'll leave this issue open in case other folks have better ideas.
The text was updated successfully, but these errors were encountered: