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

Add loading/error states (skeleton loaders and error messages) to Batch and Analytics pages #414

New Issue
Closed
opened 2026-03-27 18:24:22 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 18:24:22 +00:00
Owner
Copy Link
Copy Source

Summary

The Batch and Analytics pages have no loading indicators or user-friendly error states. Users see a blank/broken page while data loads or if a request fails.

What to do

  1. Add skeleton loader components (can use a Tailwind-based shimmer or a library like react-loading-skeleton) to the Batch and Analytics pages while API calls are in-flight
  2. Add an error boundary or inline error message that displays when an API call fails, with a retry button
  3. Ensure the loading and error states are consistent with any existing patterns in other pages

Acceptance Criteria

  • Navigating to the Batch page shows a skeleton while data loads, not a blank area
  • Navigating to the Analytics page shows a skeleton while charts load
  • A simulated API failure (e.g., network offline) shows an inline error message with a retry button
  • No console errors during loading or error states

Reference

Roadmap: P2 - Frontend / Loading and error states

## Summary The Batch and Analytics pages have no loading indicators or user-friendly error states. Users see a blank/broken page while data loads or if a request fails. ## What to do 1. Add skeleton loader components (can use a Tailwind-based shimmer or a library like `react-loading-skeleton`) to the Batch and Analytics pages while API calls are in-flight 2. Add an error boundary or inline error message that displays when an API call fails, with a retry button 3. Ensure the loading and error states are consistent with any existing patterns in other pages ## Acceptance Criteria - Navigating to the Batch page shows a skeleton while data loads, not a blank area - Navigating to the Analytics page shows a skeleton while charts load - A simulated API failure (e.g., network offline) shows an inline error message with a retry button - No console errors during loading or error states ## Reference Roadmap: P2 - Frontend / Loading and error states
AI-Manager added the P2agent-readymedium labels 2026-03-27 18:24:22 +00:00
AI-Manager commented 2026-03-27 19:07:17 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

Both the Batch and Analytics pages already have:

  • Skeleton loading states with animate-pulse shimmer effects
  • Error states with descriptive messages and retry buttons
  • Loading spinners during mutation/submit operations

This issue can be closed.

## Triage: Already Implemented Both the Batch and Analytics pages already have: - Skeleton loading states with `animate-pulse` shimmer effects - Error states with descriptive messages and retry buttons - Loading spinners during mutation/submit operations This issue can be closed.
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#414
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?