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

[hussam789]

User description

PR #10

---

PR Type

Enhancement

---

Description

• Add calendar cache status tracking with updatedAt timestamp

• Implement cache deletion functionality via new tRPC endpoint

• Create CredentialActionsDropdown component for cache management UI

• Integrate cache status into connectedCalendars response

• Add translation strings for cache-related user messages

---

Diagram Walkthrough

flowchart LR
  A["CalendarCache Schema"] -->|updatedAt field| B["CalendarCacheRepository"]
  B -->|getCacheStatusByCredentialIds| C["connectedCalendars Handler"]
  C -->|cacheUpdatedAt enrichment| D["CredentialActionsDropdown"]
  D -->|deleteCache mutation| E["deleteCacheHandler"]
  E -->|delete operation| F["Prisma CalendarCache"]

Loading

File Walkthrough

	Relevant files
Schema changes	1 files schema.prisma Add updatedAt timestamp field to CalendarCache                      +2/-0
Database migration	1 files migration.sql Database migration for CalendarCache updatedAt column        +9/-0
Interface enhancement	1 files calendar-cache.repository.interface.ts Add getCacheStatusByCredentialIds method signature              +3/-0
Repository implementation	1 files calendar-cache.repository.ts Implement getCacheStatusByCredentialIds with groupBy query +17/-0
Testing utilities	2 files calendar-cache.repository.mock.ts Add mock implementation for getCacheStatusByCredentialIds +5/-0      test-gcal-webhooks.sh New script for testing Google Calendar webhooks with Tunnelmole +79/-0
Repository enhancement	1 files selectedCalendar.ts Add updateManyByCredentialId method and fix type issues    +8/-2
Query enhancement	1 files user.ts Include updatedAt and googleChannelId in selectedCalendars query +2/-0
Type definition enhancement	1 files getConnectedDestinationCalendars.ts Extend UserWithCalendars type with cache-related fields    +8/-2
Service enhancement	1 files CalendarService.ts Update SelectedCalendar timestamps after availability sync +3/-0
Router enhancement	1 files _router.tsx Add deleteCache tRPC endpoint to calendars router                +9/-0
Handler enhancement	1 files connectedCalendars.handler.ts Enrich connectedCalendars response with cache status data +13/-1
New handler	1 files deleteCache.handler.ts New handler for deleting calendar cache by credential        +33/-0
New component	1 files CredentialActionsDropdown.tsx New dropdown component for credential and cache actions    +157/-0
Component replacement	1 files SelectedCalendarsSettingsWebWrapper.tsx Replace DisconnectIntegration with CredentialActionsDropdown +23/-25
Localization	1 files common.json Add translation strings for cache status and deletion        +7/-0
Configuration changes	1 files package.json Update dev:cron script to use npx tsx instead of ts-node  +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Insufficient auditing Description: The deleteCache handler throws a generic Error string on auth failure and returns generic success, lacking granular error types and rate limiting; while authorization is checked, absence of audit/logging for destructive action could hinder incident response. deleteCache.handler.ts [13-32] Referred Code export const deleteCacheHandler = async ({ ctx, input }: DeleteCacheOptions) => { const { user } = ctx; const { credentialId } = input; const credential = await prisma.credential.findFirst({ where: { id: credentialId, userId: user.id, }, }); if (!credential) { throw new Error("Credential not found or access denied"); } await prisma.calendarCache.deleteMany({ where: { credentialId }, }); return { success: true };
	Unsafe file write Description: The script writes/updates GOOGLE_WEBHOOK_URL in a relative ../.env file and parses tmole output without strict validation, which could overwrite unintended env files if run from unexpected cwd. test-gcal-webhooks.sh [61-71] Referred Code # Update env file if [ ! -f "$ENV_FILE" ]; then echo "⚠️ $ENV_FILE not found. Creating new file." touch "$ENV_FILE" fi if grep -q '^GOOGLE_WEBHOOK_URL=' "$ENV_FILE"; then sed -i '' -E "s|^GOOGLE_WEBHOOK_URL=.*|GOOGLE_WEBHOOK_URL=$TUNNEL_URL|" "$ENV_FILE" else echo "GOOGLE_WEBHOOK_URL=$TUNNEL_URL" >> "$ENV_FILE" fi
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Missing audit log: Deleting cache is a critical action but the new handler performs the deletion without emitting any audit log including user, credential, or outcome context. Referred Code export const deleteCacheHandler = async ({ ctx, input }: DeleteCacheOptions) => { const { user } = ctx; const { credentialId } = input; const credential = await prisma.credential.findFirst({ where: { id: credentialId, userId: user.id, }, }); if (!credential) { throw new Error("Credential not found or access denied"); } await prisma.calendarCache.deleteMany({ where: { credentialId }, }); return { success: true };
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Generic error thrown: The handler throws a generic Error string for missing/unauthorized credential and does not handle possible failures from deleteMany or validate input edge cases. Referred Code if (!credential) { throw new Error("Credential not found or access denied"); } await prisma.calendarCache.deleteMany({ where: { credentialId }, });
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Info leakage risk: The error message "Credential not found or access denied" may reveal the existence of a credential to an attacker depending on routing; consider a uniform generic message for end users. Referred Code if (!credential) { throw new Error("Credential not found or access denied"); }

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Fix no-op database update call Explicitly set the updatedAt field in the updateManyByCredentialId call to ensure the timestamp is updated, as passing an empty object results in a no-op. packages/app-store/googlecalendar/lib/CalendarService.ts [1023-1024] // Update SelectedCalendar.updatedAt for all calendars under this credential -await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, {}); +await SelectedCalendarRepository.updateManyByCredentialId(this.credential.id, { updatedAt: new Date() }); Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a bug where an update operation is a no-op, preventing the updatedAt field from being updated as intended, and provides the correct fix.	Medium
General	Use dynamic locale for date formatting Replace the hardcoded "en-US" locale in Intl.DateTimeFormat with the dynamic language variable from the useLocale hook to ensure dates are formatted according to the user's selected language. packages/features/apps/components/CredentialActionsDropdown.tsx [88-94] {t("cache_last_updated", { - timestamp: new Intl.DateTimeFormat("en-US", { + timestamp: new Intl.DateTimeFormat(language, { dateStyle: "short", timeStyle: "short", }).format(new Date(cacheUpdatedAt)), interpolation: { escapeValue: false }, })} Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out a hardcoded "en-US" locale for date formatting, which harms internationalization. Using the dynamic locale from the useLocale hook is a good improvement for user experience.	Medium
More

[bar-qodo]

@greptile review