caldav: support more features for recurring events#105
Draft
bitfehler wants to merge 1 commit intoemersion:masterfrom
Draft
caldav: support more features for recurring events#105bitfehler wants to merge 1 commit intoemersion:masterfrom
bitfehler wants to merge 1 commit intoemersion:masterfrom
Conversation
Collaborator
Author
|
This is not finished, but since this touches the exported API, can you let me know whether this approach makes sense to you? |
bitfehler
force-pushed
the
bitfehler/recurrence-limits
branch
from
eaba278 to
ac2e356
Compare
The protocol allows clients to ask the server to e.g. expand recurring events to a set of simple events in a given time-frame, so that the client does not have to calculate the recurrences. This commit adds the foundation for support for expand [1], limit-recurrence-set [2], and limit-freebusy-set [3] functionality. However, the actual transformation of events returned to clients will have to be implemented in the backend, which now has the required information to do so. [1]: https://datatracker.ietf.org/doc/html/rfc4791#section-9.6.5 [2]: https://datatracker.ietf.org/doc/html/rfc4791#section-9.6.6 [3]: https://datatracker.ietf.org/doc/html/rfc4791#section-9.6.7
bitfehler
force-pushed
the
bitfehler/recurrence-limits
branch
from
ac2e356 to
a5ea3ab
Compare
|
Any plans or blockers to progress this PR? Support for recurring meetings would be awesome. |
Contributor
Seems like the other guy opened this pull request two years ago... but I just opened another pull request that adds the expand prop in #167, hope it helps! |
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The protocol allows clients to ask the server to e.g. expand recurring
events to a set of simple events in a given time-frame, so that the
client does not have to calculate the recurrences.
This commit adds the foundation for support for expand 1,
limit-recurrence-set 2, and limit-freebusy-set 3 functionality.
However, the actual transformation of events returned to clients will
have to be implemented in the backend, which now has the required
information to do so.