-
- [ ] Parser
- [ ] Additional Tags & Properties
-
### 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…
-
As a steward, I'd like to be able to see all RSVPs for all events. Can we have all current stewards (no more than 6 steward email addresses) receive access to see all RSVPs for all Convo Events by def…
-
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…
-
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…
-
There is an issue when parsing an RRULE string that does not begin with "FREQ". The current parser extracts the first occurrence of "FREQ" and everything following it, meaning that any properties that…
-
### 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
…
-
According to RFC 5545, every VCAL needs a `PRODID` and `VERSION`. If those are not explicitly added, `Calendar.to_ical()` produces non-conforming output because they are missing.
It could be a de…
-
`https://fpira.com/calendars/posts.ics` cannot be parsed due to bad line feeds
check line endings to comply with https://icalendar.org/iCalendar-RFC-5545/3-1-content-lines.html.
Then validate ou…
-
the iCalendar format produced by this Component does not conform to the [RFC 5545](https://tools.ietf.org/html/rfc5545#section-3.1) specification with regards to line "folding" and line break escapeme…