P1: Frontend api.js does not handle CORS errors — generic error message shown #10
Labels
No Label
P0 Critical
P1 High
P2 Medium
P3 Low
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
performance
phase-7
phase-8
security
seo
ui
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#10
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?
Severity: P1 — High
File: src/lib/api.js ~line 8
Problem: If CORS blocks a request, fetch() throws TypeError but frontend catches it as a generic error. No distinction between network errors, CORS failures, and backend errors.
Impact: Developer confusion when CORS is misconfigured in production.
Fix: Add specific error type detection and user-friendly messages for CORS/network errors.