Do not display fabricated work items when context fetch fails #105

Closed
opened 2026-08-06 12:46:22 +00:00 by timmy · 0 comments
Owner

Evidence: the dashboard context fetch catch block currently injects hard-coded issues #1, #8, #37 and PR #4. During a network or HTTP failure, users therefore see invented work as if it were current. Replace these fixtures with explicit unavailable states so operational failures cannot be mistaken for live Gitea data.

Evidence: the dashboard context fetch catch block currently injects hard-coded issues #1, #8, #37 and PR #4. During a network or HTTP failure, users therefore see invented work as if it were current. Replace these fixtures with explicit unavailable states so operational failures cannot be mistaken for live Gitea data.
timmy self-assigned this 2026-08-06 12:46:22 +00:00
timmy closed this issue 2026-08-06 12:47:54 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#105
No description provided.