feat: add calendar cache status and actions (#22532)

[zaibkhan]

No description provided.

[codoki-pr-intelligence]

Codoki PR Review

Summary: Ensure cache timestamp updates, prevent stale status
What’s good: Solid addition of cache status plumbing: new repository method, mock parity, and Prisma @updatedat on CalendarCache improve observability; UI strings and connectedCalendars selection fields align with the feature.
Review Status: ✅ Safe to merge
Review Update:
• Coverage: Reviewed all 17 files across 2 batches

Issues (Medium)

Severity	Issue	Why it matters
Medium	Correctness — Stale UI after cache deletion due to missing invalidation	…/components/CredentialActionsDropdown.tsx After deleting cache, the connectedCalendars list isn't invalidated, so cacheUpdatedAt can remain stale until a manual reload. Add an onSettled to invalidate connectedCalendars (and optionally integrations) and move the useUtils() declaration above this mutation so it can be referenced here.
Medium	Compatibility — sed -i usage is not portable across macOS/Linux	scripts/test-gcal-webhooks.sh This sed invocation is BSD/macOS-specific and will fail on GNU sed (Linux). Use an OS-aware branch to ensure portability.

Showing up to 2 medium issue(s). See inline suggestions for more details.

Key Feedback (click to expand)

• Needs improvement: In GoogleCalendarService, updating SelectedCalendar timestamps with an empty data payload may be a no-op; explicitly set updatedAt or ensure the repository bumps timestamps when data is empty to avoid misleading 'Last updated'.
• Testing: Add an integration test for refresh path verifying SelectedCalendar.updatedAt actually changes post-refresh and that UI renders the new timestamp; include a negative case when repository throws to ensure failures don't mask cache writes. Also test that getCacheStatusByCredentialIds surfaces expected timestamps and that the mock returns an empty array without errors when calendar cache is disabled.
• Documentation: Document in SelectedCalendarRepository.updateManyByCredentialId whether passing {} is intended to bump updatedAt and, if so, mention reliance on Prisma @updatedat vs explicit field updates. Clarify in the handler/service whether updates apply to all calendars under a credential or only those processed.
• Compatibility: No backward-compatibility issues detected; added fields are optional reads and new repository method is additive.
• Performance: The extra updateMany call per refresh is acceptable; if this runs frequently, consider scoping updates to just affected calendar IDs to avoid unnecessary writes.
• Security: No new security surfaces identified in the provided diffs.
• Open questions: Should we update only the SelectedCalendars that were actually refreshed, rather than all under the credential, to better reflect per-calendar cache freshness?

Confidence: 4/5 — Looks good; minor fixes (4 medium)

React with 👍 or 👎 if you found this review useful.

[codoki-pr-intelligence]

🔷 Medium: After deleting cache, the connectedCalendars list isn't invalidated, so cacheUpdatedAt can remain stale until a manual reload. Add an onSettled to invalidate connectedCalendars (and optionally integrations) and move the useUtils() declaration above this mutation so it can be referenced here.

diff

• const deleteCacheMutation = trpc.viewer.calendars.deleteCache.useMutation({

• const deleteCacheMutation = trpc.viewer.calendars.deleteCache.useMutation({
  onSuccess: () => {
  showToast(t("cache_deleted_successfully"), "success");
  onSuccess?.();
  },
  onError: () => {
  showToast(t("error_deleting_cache"), "error");
  },
• async onSettled() {

•  await utils.viewer.calendars.connectedCalendars.invalidate();
  

• },
  });

[codoki-pr-intelligence]

🔷 Medium: This sed invocation is BSD/macOS-specific and will fail on GNU sed (Linux). Use an OS-aware branch to ensure portability.

diff

• sed -i '' -E "s|^GOOGLE_WEBHOOK_URL=.*|GOOGLE_WEBHOOK_URL=$TUNNEL_URL|" "$ENV_FILE"

• if [[ "$OSTYPE" == "darwin"* ]]; then
• sed -i '' -E "s|^GOOGLE_WEBHOOK_URL=.*|GOOGLE_WEBHOOK_URL=$TUNNEL_URL|" "$ENV_FILE"
• else
• sed -i -E "s|^GOOGLE_WEBHOOK_URL=.*|GOOGLE_WEBHOOK_URL=$TUNNEL_URL|" "$ENV_FILE"
• fi

[codoki-pr-intelligence]

🔷 Medium: Passing an empty update object may not trigger any write, so SelectedCalendar.updatedAt might not change, leaving the UI with a stale 'Last updated' value. Either have the repository explicitly bump updatedAt when data is empty or set it here to guarantee the timestamp updates. Also consider scoping the update to only calendars actually refreshed to avoid misleading statuses.

Suggested change

	await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, {});
	await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, { updatedAt: new Date() });