| Issue 2166: | eventSourceDataTransform to preprocess event data (such as JSON) | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Similare to eventDataTransform: http://arshaw.com/fullcalendar/docs/event_data/eventDataTransform/ ...but given the root object (be it an array of events, or some higher-level object), and will return an array of events for fullcalendar to use. Will be a robust solution for solving problems such as Issue 1733
Jun 5, 2014
Project Member
#1
adamrs...@gmail.com
Jun 19, 2014
one implementation (called something different): https://github.com/arshaw/fullcalendar/pull/173
Sep 5, 2014
Issue 2274 has been merged into this issue.
Dec 3, 2014
The eventDataTransform does not give me the chance to discard any incoming json objects. The flow goes like this : 1.you call the server for events, who will have an unknown json structure 2.eventDataTransform kicks in to map the json to fullCalendar eventObjects 3.what if i encounter some events that I want to consider illegal? and discard them? The eventDataTransform does not do this, it returns a default eventObject if the return of the transformer is null or false. Ideally the eventDataTransform would not map an eventObject if the transformer returns false.
Dec 14, 2014
@LorenGRX, can you open up a new issue regarding your proposed enhanced behavior about eventDataTransform? We'll keep this issue focused on eventSourceDataTransform.
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/2431 This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event. Happy coding, Adam
Status:
ExportedToGithub
|
|
| ► Sign in to add a comment |