-
The RFC 5545 describes all the properties we have in icalendar.prop.
Please add a `__doc__` string documentation for all of them.
Examples:
- [vMonth](https://icalendar.readthedocs.io/en/late…
-
When opening an .ics file (that was even validated by [https://icalendar.org/validator.html](https://icalendar.org/validator.html) to comply to RFC 5545) with Calendar, Calendar crashes. Error log, Ca…
-
- [ ] Parser
- [ ] Additional Tags & Properties
-
# Bug report
### Bug description:
Custom properties in VTIMEZONE are allowed according to [RFC 5545](https://www.rfc-editor.org/rfc/rfc5545.html#section-3.6.5). However they create an error in `…
-
Currently, the organizer field seems to be wrong when using the sent-by parameter.
According to [RFC 5545](https://datatracker.ietf.org/doc/html/rfc5545#section-3.2.18): The individual calendar add…
-
### Issue
As per [RFC 5545](https://tools.ietf.org/html/rfc5545#section-3.8.4.7) every VEVENT, VTODO, and VJOURNAL entry must have a unique identifier (UID). This module does not currently implemen…
-
It seems that in the [RFC 5545 spec](https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.5.3), when the `TZID` parameter is provided, `DTSTART` should be specified in that timezone (i.e., not UT…
-
recurring-ical-events should also be able to calculate when alarms take place.
Component: VALARM
[RFC 5545](https://www.rfc-editor.org/rfc/rfc5545.html):
- [ ] single alarm
- [ ] repeating a…
-
Similar to ICAL.Event, there should be an ICAL.ToDo item that handles the VTODO component as described in section 3.6.2 ("To-Do Component") of RFC 5545 or at https://icalendar.org/iCalendar-RFC-5545/3…
-
### Checklist
Please mark these items with an [x]
- [ x] I've already searched through [existing tickets](https://fullcalendar.io/issues)
- [ x] Other people will find this feature useful
…