fix: single rejection caused cache cron to fail #18239
Merged
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.
What does this PR do?
follow up to #18237 #18224
This pull request includes changes to improve the handling of calendar subscriptions and simplify the repository code. The most important changes include modifying the way promises are handled in the
handleCalendarsToWatch
function, removing unnecessary feature repository checks, and updating theSelectedCalendarRepository
class.Improvements to calendar subscription handling:
packages/features/calendar-cache/api/cron.ts
: Changed from usingPromise.all
toPromise.allSettled
for handling calendar watch and unwatch operations, and simplified the response object by removing detailed success/failure counts.Codebase simplification:
packages/lib/server/repository/selectedCalendar.ts
: Removed the import and usage ofFeaturesRepository
and the associated feature check for "calendar-cache", simplifying the conditions for unwatching subscriptions. [1] [2] [3]Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
Checklist