summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfpi2024-09-17 22:06:06 +0200
committerfpi2024-09-17 22:06:06 +0200
commit69da7524276bf90abb56c79234c69b0607ee5262 (patch)
tree97b7104e0ebf093804ad3c17362905014d966ddb
parentEnsure proper property value quoting (diff)
Document problems with current ical-event class
-rw-r--r--README.org2
-rw-r--r--gnus-icalendar-request-tests.el3
2 files changed, 4 insertions, 1 deletions
diff --git a/README.org b/README.org
index a568b6b..5cc0461 100644
--- a/README.org
+++ b/README.org
@@ -19,3 +19,5 @@ Extension of gnus-icalendar to format icalendar event requests based on [[https:
- [X] Check attendee capturing from email ~From~ header.
- [ ] Based on insertion method remove the multipart section or switch ~multipart/alternative~ if ~text/plain~ contains the same data as the ~text/calendar~ part.
- [X] +Split default attendee line format into a ~defvar~ in ~gnus-icalendar--format-attendee~.+
+- [ ] The updated rich cons I use to transfer mail + CN data does not fit with the ~gnus-icalendar-event object~ expectations, where all other functions only expect a list of strings for these fields. How can we fix this?
+ - Currently ~gnus-icalendar-event-from-buffer~ destroys attendee data and only returns the CN if present or the email but never both.
diff --git a/gnus-icalendar-request-tests.el b/gnus-icalendar-request-tests.el
index 413cbd3..b9a2954 100644
--- a/gnus-icalendar-request-tests.el
+++ b/gnus-icalendar-request-tests.el
@@ -69,7 +69,8 @@ DTSTART:20240917T080000Z
DTEND:20240917T100000Z
SUMMARY:Party
DESCRIPTION:Lots of reasons to celebrate!
-ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:required@company.invalid
+ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE;CN=Required CN:mailto:required@company.invalid
+ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;RSVP=TRUE:mailto:required2@company.invalid
ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=OPT-PARTICIPANT;RSVP=TRUE:mailto:optional@company.invalid
LOCATION:Party room
ORGANIZER:mailto:organizer@company.invalid