🧹 Add error logging to legacy cache cleanup catch block - #47
Conversation
Replaced empty catch block in `removeLegacyCollegeCaches` with `errorLoggingService.captureException` to track potential storage errors while maintaining best-effort (non-blocking) behavior.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🎯 What: Modified
removeLegacyCollegeCachesto capture and log errors instead of swallowing them in an empty catch block.💡 Why: Empty catch blocks hide bugs. By leveraging the existing
errorLoggingService.captureException, we gain visibility into local storage issues without blocking the main college data retrieval flow.✅ Verification: Ran
npm run typecheck,npm run lint, andnpm run test:appto ensure the changes are syntactically valid and introduce no regressions.✨ Result: Improved codebase observability and health without modifying functionality.
PR created automatically by Jules for task 18306299539876117992 started by @MarsLuay