-
Notifications
You must be signed in to change notification settings - Fork 168
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
Timeline: support for ISO Date strings #57
Comments
For what it's worth, I can see where to put the change, so if you want a patch for it, I'll have a go In here I think: links.Timeline.prototype.createItem = function(itemData) { I'd propose a method to parse a non-date itemData.start and itemData.end |
I would be very handy indeed when the Timeline can handle string ISO Dates. See also: https://groups.google.com/forum/#!topic/chap-links-library/pNXY7P2Bq7g |
I have updated the title of your issue, I hope you don't mind. |
JSON dates are broken. Everyone knows this.
It would be nice(!) if the handler for loading JSON data would handle the formats that are produced by .NET Json serialiser and other server side stuff without having to preprocess the data.
e.g.
A generic data format (UTC String)
{"items":[
{
"start":"2012-12-20T00:00:00+00:00",
"end":"2012-12-28T00:00:00+00:00",
"content":"Content",
"group":"Group1",
"className":"itemclass"
}
]}
Or the .NET default representation of number of milliseconds since January 1st 1970 UTC
{"items":[
{"start":"/Date(1355961600000)/",
"end":"/Date(1356652800000)/",
"content":"Content",
"group":"Group1",
"className":"itemclass"
}
]}
The text was updated successfully, but these errors were encountered: