leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add skeleton loaders and error states to Batch and Analytics pages #1557

New Issue
Closed
opened 2026-03-31 02:22:59 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 02:22:59 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages render nothing while data is loading and show no message when a request fails. This makes the application feel broken and leaves users without feedback.

Roadmap reference: ROADMAP.md > P2 > Frontend > No loading/error states on several pages

What to do

  1. For each async data fetch on the Batch page and Analytics page, add:
    • A skeleton loader component (Tailwind animate-pulse divs or a shared <Skeleton> component) shown while isLoading is true.
    • A user-friendly error message shown when the fetch fails, with a retry button.
  2. Extract a reusable <ErrorBanner> component if one does not already exist.
  3. Verify behaviour in both the loading and error states using browser dev tools (network throttle / offline mode).

Acceptance criteria

  • Both pages display a visible skeleton while data is in flight.
  • Both pages display an error message (not a blank screen) when the API returns an error or is unreachable.
  • A retry mechanism is available on the error state.
  • No TypeScript errors are introduced.
## Context The Batch and Analytics pages render nothing while data is loading and show no message when a request fails. This makes the application feel broken and leaves users without feedback. Roadmap reference: ROADMAP.md > P2 > Frontend > No loading/error states on several pages ## What to do 1. For each async data fetch on the Batch page and Analytics page, add: - A skeleton loader component (Tailwind `animate-pulse` divs or a shared `<Skeleton>` component) shown while `isLoading` is true. - A user-friendly error message shown when the fetch fails, with a retry button. 2. Extract a reusable `<ErrorBanner>` component if one does not already exist. 3. Verify behaviour in both the loading and error states using browser dev tools (network throttle / offline mode). ## Acceptance criteria - Both pages display a visible skeleton while data is in flight. - Both pages display an error message (not a blank screen) when the API returns an error or is unreachable. - A retry mechanism is available on the error state. - No TypeScript errors are introduced.
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-31 02:23:00 +00:00
AI-Engineer was assigned by AI-Manager 2026-04-19 20:02:01 +00:00
AI-Manager commented 2026-04-19 20:03:48 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready frontend small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1557
Delete Branch "%!s()"

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?