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

Add loading skeletons and error states to Batch and Analytics pages #1205

New Issue
Closed
opened 2026-03-30 04:24:02 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 04:24:02 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages do not show loading indicators or user-friendly error messages. Users see blank or broken UI while data is fetching or when a request fails.

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

What to do

  1. Add skeleton loader components to the Batch page while job list is loading.
  2. Add skeleton loaders to the Analytics page while chart data is loading.
  3. Add error boundary or inline error messages when API calls fail on both pages.
  4. Use consistent patterns (e.g., a shared <LoadingState> and <ErrorState> component).

Acceptance criteria

  • Batch page shows a skeleton while the job list loads.
  • Analytics page shows a skeleton while chart data loads.
  • Both pages display a user-friendly error message when the API returns an error.
  • No raw stack traces or empty white boxes are shown to users.
## Context The Batch and Analytics pages do not show loading indicators or user-friendly error messages. Users see blank or broken UI while data is fetching or when a request fails. Roadmap reference: ROADMAP.md > P2 > Frontend > No loading/error states on several pages ## What to do 1. Add skeleton loader components to the Batch page while job list is loading. 2. Add skeleton loaders to the Analytics page while chart data is loading. 3. Add error boundary or inline error messages when API calls fail on both pages. 4. Use consistent patterns (e.g., a shared `<LoadingState>` and `<ErrorState>` component). ## Acceptance criteria - [ ] Batch page shows a skeleton while the job list loads. - [ ] Analytics page shows a skeleton while chart data loads. - [ ] Both pages display a user-friendly error message when the API returns an error. - [ ] No raw stack traces or empty white boxes are shown to users.
AI-Manager added the P2agent-readymediumfrontend labels 2026-03-30 04:24:02 +00:00
AI-Manager commented 2026-03-30 05:04:53 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved on main. frontend/src/pages/Batch.tsx includes loading skeleton components (line 294) and frontend/src/pages/Analytics.tsx includes skeleton cards and skeleton charts (lines 31, 40). Closing as complete.

This issue has been resolved on main. `frontend/src/pages/Batch.tsx` includes loading skeleton components (line 294) and `frontend/src/pages/Analytics.tsx` includes skeleton cards and skeleton charts (lines 31, 40). Closing as complete.
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 medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1205
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?