fix(caldav): add EXDATE and EXRULE to confidential object #44360
Conversation
This file contains 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
miaulalala
added
bug
3. to review
|
/backport to stable28 |
|
/backport to stable27 |
|
/backport to stable26 |
kesselb
approved these changes
Mar 20, 2024
Merged
tcitworld
reviewed
Mar 20, 2024
miaulalala
force-pushed
the
fix/add-exdate-exrule-to-confidential-object
branch
from
2c2165c
to
9999f15
Compare
Signed-off-by: Anna Larch <anna@nextcloud.com>
miaulalala
force-pushed
the
fix/add-exdate-exrule-to-confidential-object
branch
from
9999f15
to
a96f8f7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The EXDATE / EXRULE properties are lost when a confidential object is created.
Checklist