feat: replace RDATE with individual VEVENTS #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.