You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the event.icalendar_instance property, but then we also have a event.icalendar_object() method which returns the (sub)component of the icalendar instance. This is quite inconsistent and confusing.
RFC 5545 is consistently using the phrasing "component", and never "subcomponent". I think the proper name for the latter is event.icalendar_component - and for the sake of consistency, it should be a property, not a method. (however, event.icalendar_object needs to persist for quite some years yet for backward compatibility reasons).
The text was updated successfully, but these errors were encountered:
Actually, icalendar_object was named _icalendar_object in v0.10, hence we don't need to worry about backward compatibility. The icalendar_component-property will be released in v0.11, but documentation needs to be fixed before the issue can be closed. Should also take a look through the example code and see if it can be used there.
We have the
event.icalendar_instance
property, but then we also have aevent.icalendar_object()
method which returns the (sub)component of the icalendar instance. This is quite inconsistent and confusing.RFC 5545 is consistently using the phrasing "component", and never "subcomponent". I think the proper name for the latter is
event.icalendar_component
- and for the sake of consistency, it should be a property, not a method. (however,event.icalendar_object
needs to persist for quite some years yet for backward compatibility reasons).The text was updated successfully, but these errors were encountered: