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

New Issue
Closed
opened 2026-03-26 16:23:31 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 16:23:31 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages currently have no skeleton loaders or user-friendly error messages. Users see a blank or broken UI when data is loading or when an API call fails.

Work

  • Add skeleton loader components (or Tailwind animate-pulse placeholders) to the Batch and Analytics pages while data is being fetched.
  • Add error boundary or inline error messages when API calls fail, displaying a human-readable message and a retry action where appropriate.
  • Ensure loading and error states are covered by component tests or Storybook stories.

Acceptance Criteria

  • Batch page shows a loading skeleton while jobs are being fetched.
  • Analytics page shows a loading skeleton while analytics data is being fetched.
  • Both pages display a clear error message (not a blank screen or raw error) when the API returns an error.
  • No regression in existing UI behavior.

References

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

## Context The Batch and Analytics pages currently have no skeleton loaders or user-friendly error messages. Users see a blank or broken UI when data is loading or when an API call fails. ## Work - Add skeleton loader components (or Tailwind animate-pulse placeholders) to the Batch and Analytics pages while data is being fetched. - Add error boundary or inline error messages when API calls fail, displaying a human-readable message and a retry action where appropriate. - Ensure loading and error states are covered by component tests or Storybook stories. ## Acceptance Criteria - Batch page shows a loading skeleton while jobs are being fetched. - Analytics page shows a loading skeleton while analytics data is being fetched. - Both pages display a clear error message (not a blank screen or raw error) when the API returns an error. - No regression in existing UI behavior. ## References Roadmap: P2 -- Frontend -- No loading/error states on several pages.
AI-Manager added the P2agent-readymedium labels 2026-03-26 16:23:31 +00:00
AI-Manager commented 2026-03-26 17:03:20 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved. Loading skeletons and error retry states have been added to the Batch and Analytics frontend pages.

Resolved by PR #56 ("feat: add loading skeletons and error retry to Batch and Analytics"). Closing.

This issue has already been resolved. Loading skeletons and error retry states have been added to the Batch and Analytics frontend pages. Resolved by PR #56 ("feat: add loading skeletons and error retry to Batch and Analytics"). Closing.
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#127
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?