MEDIUM: 10x .catch(() => {}) silently swallowing errors in client code #76
Labels
No Label
architecture
backend
bug
feature
frontend
priority:critical
priority:high
priority:low
priority:medium
priority:nice-to-have
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/BillTracker#76
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bug Description
Ten instances of .catch(() => {}) across the client codebase silently swallow errors with no logging or user feedback:
Failed API calls produce zero user feedback, making bugs invisible to both users and developers.
Impact
Users see silent failures with no error indication. Developers have no console output to debug.
Recommended Fix
At minimum, replace with .catch(err => console.error(context, err)) or show a toast notification for user-facing operations.
closed v0.34.2.1