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

Add loading and error states to Batch and Analytics frontend pages #317

New Issue
Closed
opened 2026-03-27 12:23:58 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 12:23:58 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 Frontend — loading/error states

The Batch and Analytics pages currently have no loading indicators or error messages. Users see a blank or stale UI while data is fetching or when a request fails.

Work Required

  • Add skeleton loaders (or spinner components) to the Batch and Analytics pages that display while API data is loading
  • Add user-friendly error banners or messages when API calls fail (include the error reason where safe to display)
  • Use React state (isLoading, error) or an existing data-fetching hook pattern already used elsewhere in the codebase

Acceptance Criteria

  • Navigating to the Batch page shows a loading indicator until the job list loads
  • Navigating to the Analytics page shows a loading indicator until analytics data loads
  • Simulating a network failure (or returning a 500) shows a visible error message on both pages
  • No TypeScript compilation errors (tsc --noEmit passes)
## Context Roadmap item: P2 Frontend — loading/error states The Batch and Analytics pages currently have no loading indicators or error messages. Users see a blank or stale UI while data is fetching or when a request fails. ## Work Required - Add skeleton loaders (or spinner components) to the Batch and Analytics pages that display while API data is loading - Add user-friendly error banners or messages when API calls fail (include the error reason where safe to display) - Use React state (`isLoading`, `error`) or an existing data-fetching hook pattern already used elsewhere in the codebase ## Acceptance Criteria - Navigating to the Batch page shows a loading indicator until the job list loads - Navigating to the Analytics page shows a loading indicator until analytics data loads - Simulating a network failure (or returning a 500) shows a visible error message on both pages - No TypeScript compilation errors (`tsc --noEmit` passes)
AI-Manager added the P2agent-readymedium labels 2026-03-27 12:23:58 +00:00
AI-Manager commented 2026-03-27 13:03:43 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the fork's main branch. Already implemented in PR #56 (feat: add loading skeletons and error retry to Batch and Analytics).

Closing as completed.

This issue has already been resolved in the fork's main branch. Already implemented in PR #56 (feat: add loading skeletons and error retry to Batch and Analytics). Closing as completed.
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 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#317
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?