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 #952

New Issue
Closed
opened 2026-03-29 09:23:51 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 09:23:51 +00:00
Owner
Copy Link
Copy Source

Background

The Batch and Analytics pages fetch data asynchronously but show no feedback while loading and no user-friendly message on failure. This leads to blank screens or silent failures.

Task

  1. Add skeleton loaders (or a spinner) to the Batch and Analytics pages that display while data is being fetched.
  2. Add error boundary or inline error messages that display when a fetch fails, with a retry affordance.
  3. Use the existing Tailwind setup for styling.

Acceptance Criteria

  • A loading indicator is visible between the moment the page mounts and data arrives.
  • When a fetch fails, a user-readable error message is displayed.
  • No blank/white screen is shown during loading or on error.

Reference

Roadmap: P2 Frontend -- No loading/error states on several pages.

## Background The Batch and Analytics pages fetch data asynchronously but show no feedback while loading and no user-friendly message on failure. This leads to blank screens or silent failures. ## Task 1. Add skeleton loaders (or a spinner) to the Batch and Analytics pages that display while data is being fetched. 2. Add error boundary or inline error messages that display when a fetch fails, with a retry affordance. 3. Use the existing Tailwind setup for styling. ## Acceptance Criteria - [ ] A loading indicator is visible between the moment the page mounts and data arrives. - [ ] When a fetch fails, a user-readable error message is displayed. - [ ] No blank/white screen is shown during loading or on error. ## Reference Roadmap: P2 Frontend -- No loading/error states on several pages.
AI-Manager added the P2agent-readymediumfeature labels 2026-03-29 09:23:51 +00:00
AI-Manager commented 2026-03-29 10:04:31 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved. Commit history shows PR #352 merged 'feat: add loading skeletons and error states to Batch page'. The Batch page now has loading skeletons, error states, and empty states. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved. Commit history shows PR #352 merged 'feat: add loading skeletons and error states to Batch page'. The Batch page now has loading skeletons, error states, and empty states. Closing as already implemented.
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 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#952
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?