My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1900: Rethink how start/end datetimes are sent
2 people starred this issue and may be notified of changes. Back to list
Status:  Released
Owner:  ----
Closed:  Jun 2014


Sign in to add a comment
 
Reported by sw360...@gmail.com, Jul 3, 2013
Parameters start/end are sent in Unix epoch time but in seconds.

Possible solutions:
1. use milliseconds (Strongly Advised!)
2. update documentation of fullcalendar

Aug 20, 2013
#1 pljosh.m...@gmail.com
+1 from me, I am definitely for using milliseconds everywhere: not only as parameters of request, but also when unmarshaling JSON data with dates as milliseconds.

Have spend some time tracking issue with events from server not being displayed. It turned out to be the problem with this. 

Aug 24, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Summary: Rethink how start/end datetimes are sent (was: start/end are sent in seconds)
Status: Discussing
Labels: Type-Feature
Sep 1, 2013
Project Member #3 adamrs...@gmail.com
(No comment was entered for this change.)
Labels: milestone-date
Sep 2, 2013
Project Member #4 adamrs...@gmail.com
Please read my proposal for a date system overhaul for fullcalendar, as it relates to this issue:

https://github.com/arshaw/fullcalendar/wiki/Proposal-for-a-date-system-overhaul

Please let me know what you think!
Jan 25, 2014
Project Member #6 adamrs...@gmail.com
i apologize on making comment on the wrong issue.

v2.0.0-beta was just release which sends ISO8601 dates to event feeds. more info:
http://arshaw.com/fullcalendar/wiki/Upgrading-to-2/
May 25, 2014
Project Member #7 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Jun 2, 2014
Project Member #8 adamrs...@gmail.com
version 2 has been released with this change.
http://blog.arshaw.com/1/post/2014/06/fullcalendar-2-released.html
Status: Released
Sign in to add a comment

Powered by Google Project Hosting