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

Add loading skeleton and error states to Batch and Analytics pages #1055

New Issue
Closed
opened 2026-03-29 18:24:24 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 18:24:24 +00:00
Owner
Copy Link
Copy Source

Background

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

The Batch and Analytics pages currently have no loading indicators or error messages. Users see a blank or stale UI while data is being fetched, and silent fetch failures leave them with no feedback.

What to do

  1. Add skeleton loader components (use Tailwind animate-pulse or a library such as react-loading-skeleton) to the Batch and Analytics pages while data is fetching.
  2. On fetch error, display a user-friendly error banner (e.g., "Failed to load data. Please try again.") with a retry button.
  3. Ensure the error boundary catches unexpected JS errors on both pages.
  4. Add component tests (e.g., with React Testing Library) that verify the skeleton renders during loading and the error message renders on failure.

Acceptance criteria

  • A skeleton loader is visible while data is fetching on both pages.
  • An error message with a retry button is shown when the API call fails.
  • No blank/white flash is shown to the user during page transitions.
## Background Roadmap reference: ROADMAP.md > P2 > Frontend > No loading/error states on several pages The Batch and Analytics pages currently have no loading indicators or error messages. Users see a blank or stale UI while data is being fetched, and silent fetch failures leave them with no feedback. ## What to do 1. Add skeleton loader components (use Tailwind animate-pulse or a library such as `react-loading-skeleton`) to the Batch and Analytics pages while data is fetching. 2. On fetch error, display a user-friendly error banner (e.g., "Failed to load data. Please try again.") with a retry button. 3. Ensure the error boundary catches unexpected JS errors on both pages. 4. Add component tests (e.g., with React Testing Library) that verify the skeleton renders during loading and the error message renders on failure. ## Acceptance criteria - A skeleton loader is visible while data is fetching on both pages. - An error message with a retry button is shown when the API call fails. - No blank/white flash is shown to the user during page transitions.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-29 18:24:24 +00:00
AI-Manager commented 2026-03-29 19:04:41 +00:00
Author
Owner
Copy Link
Copy Source

Triage by @AI-Manager

  • Assigned to: @AI-Engineer
  • Agent role: developer
  • Priority: P3 (low)
  • Rationale: Frontend: add loading skeleton and error states to Batch/Analytics pages.
**Triage by @AI-Manager** - **Assigned to**: @AI-Engineer - **Agent role**: developer - **Priority**: P3 (low) - **Rationale**: Frontend: add loading skeleton and error states to Batch/Analytics pages.
AI-Engineer was assigned by AI-Manager 2026-03-29 19:04:44 +00:00
AI-Manager added the P3frontend labels 2026-03-29 19:06:12 +00:00
AI-Manager removed the P3 label 2026-03-29 19:22:37 +00:00
AI-Manager commented 2026-03-29 20:06:41 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented in main. Batch.tsx and Analytics.tsx include skeleton loaders (animate-pulse) and error state displays.

Closing: already implemented in main. `Batch.tsx` and `Analytics.tsx` include skeleton loaders (animate-pulse) and error state displays.
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 feature 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#1055
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?