Removing attendee from scheduled recurring event should generate an EXDATE property #728
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #728 +/- ##
=========================================
Coverage 98.78% 98.78%
Complexity 1877 1877
=========================================
Files 71 71
Lines 5274 5274
=========================================
Hits 5210 5210
Misses 64 64 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
phil-davis
force-pushed
the
kristoffer-moellerhoej-schedule-attendee-removal
branch
from
f9b5a02 to
4bf2c58
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In the (special) case where an organizer creates a recurrent event with only one attendee and removes that attendee from one of the instances, an iTip message with an EXDATE property should be created. Currently, the EXDATE is not correctly inserted in the iTip message, this pull request fixes that.