feat: replace RDATE with individual VEVENTS#29
feat: replace RDATE with individual VEVENTS#29raphaelfloresca wants to merge 1 commit intojspricke:masterfrom
Conversation
|
Thanks for the proposal!
The problem is that
Can you be more specific which clients you tried? |
That is very true - this switch breaks the existing logic of one REM line => one VEVENT. For two-way sync (as in I'm up for spending a bit of time in the future to think about how to handle this case. Perhaps something involving a shared part of the UID across associated iCalendar events, which gets translated to a single REM line upon change on the iCalendar side?
I'm an iOS/Mac user so I've tested out |
|
I'm testing this out on I'm a little busy this month, so I'll need more time to get everything to work. Please leave the PR open for when I'm able to return to it. |
This PR takes Remind events that would normally generate a single VEVENT with multiple RDATE and splits them off into their own VEVENTs.
This addresses my issue here.
It potentially also addresses these issues re: recurring events.
#20
#21
As these issues were closed due to the fix for generating single events being 'better done outside of this lib', I'm unsure whether you'd like to merge this.
However, from testing out with multiple CalDAV clients, it seems RDATE is not widely supported, so perhaps this switch is something to consider to improve compatibility of
python-remindwith other CalDAV clients.Happy to discuss further.