perf(caldav): preload publish statuses for a whole calendar home at once #54435
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
st3iny
added
enhancement
performance 🚀
feature: caldav
st3iny
requested review from
a team,
SebastianKrupinski and
tcitworld
as code owners
st3iny
requested review from
Altahrim,
come-nc and
yemkareems
and removed request for
a team
SebastianKrupinski
approved these changes
Aug 16, 2025
come-nc
reviewed
Aug 18, 2025
AndyScherzinger
force-pushed
the
perf/caldav/preload-calendar-publish-status
branch
from
3ef9c2e to
f52e9f4
Compare
Merged
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
st3iny
force-pushed
the
perf/caldav/preload-calendar-publish-status
branch
from
f52e9f4 to
e8986db
Compare
come-nc
approved these changes
Aug 28, 2025
st3iny
added
4. to release
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
This is the last big duplicated query I could find.
The logic follows how we preload shares once for a whole calendar home. Instead of loading the publish statuses one by one for each calendar inside it.
Checklist