-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Handle wrongly cloned moments #1417
Handle wrongly cloned moments #1417
Conversation
I've tested changes on my functionality and had no issues anymore. Thanks for the commit. |
I tested these changes using Knockout's ko.toJSON(...). The following works:
However, the following still results in the same RangeError as before:
I've included the call stack in case it is any help.
|
@mattbrooks2010 yeah. I missed moment.utc. Now it works, I tested with ko and added tests. |
Confirmed - thank you. Do you know when a release will be available via NuGet? |
Handle wrongly cloned moments
Looks great |
This is in response to #1404
_.extend({}, moment())
asisMoment
-sPlease interested parties (@chilversc, @mattbrooks2010, @RomanDidenko) -- test on knockout, or whatever fancy libraries you happen to use if it works fine with them.