The icalendar library, that django-ical relies on, supports not just events but also other types of calendar contents, such as "VTODO" elements (as the Todo class, sadly not very extensively documented). Those correspond to tasks to be completed by a certain deadline, as defined by the Tasks extension of the iCalendar specification.
It seems to me that django-ical does not currently support exposing such tasks in the ical feeds it generates.
Would this functionality be in scope of this library?
For instance, I could imagine using a new method on the feed class to determine whether an entry should be translated as an Event or as a Todo:
class EventFeed(ICalFeed):
def item_type(self, item):
return "todo"Or simply using a class attribute (if calendars should not be able to contain mixes of events and tasks). Other methods would be added to support the fields that are specific to tasks.
The icalendar library, that django-ical relies on, supports not just events but also other types of calendar contents, such as "VTODO" elements (as the Todo class, sadly not very extensively documented). Those correspond to tasks to be completed by a certain deadline, as defined by the Tasks extension of the iCalendar specification.
It seems to me that django-ical does not currently support exposing such tasks in the ical feeds it generates.
Would this functionality be in scope of this library?
For instance, I could imagine using a new method on the feed class to determine whether an entry should be translated as an
Eventor as aTodo:Or simply using a class attribute (if calendars should not be able to contain mixes of events and tasks). Other methods would be added to support the fields that are specific to tasks.