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

Add loading skeletons and error states to Batch and Analytics pages #746

New Issue
Closed
opened 2026-03-28 17:23:38 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 17:23:38 +00:00
Owner
Copy Link
Copy Source

Context

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

The Batch and Analytics pages do not show loading indicators while data is fetching or display user-friendly messages when requests fail. This makes the UI feel broken during slow or failed API calls.

What to do

  1. Add skeleton loader components to the Batch and Analytics pages while data is being fetched
  2. Add error boundary or per-component error states that display a friendly message (and optionally a retry button) when an API call fails
  3. Use Tailwind CSS for styling consistent with the rest of the UI

Acceptance criteria

  • Batch page shows a skeleton/spinner while jobs are loading
  • Analytics page shows a skeleton/spinner while data is loading
  • Both pages show a user-friendly error message when the API returns an error or the request fails
  • No console errors introduced
## Context Roadmap reference: P2 - No loading/error states on several pages The Batch and Analytics pages do not show loading indicators while data is fetching or display user-friendly messages when requests fail. This makes the UI feel broken during slow or failed API calls. ## What to do 1. Add skeleton loader components to the Batch and Analytics pages while data is being fetched 2. Add error boundary or per-component error states that display a friendly message (and optionally a retry button) when an API call fails 3. Use Tailwind CSS for styling consistent with the rest of the UI ## Acceptance criteria - [ ] Batch page shows a skeleton/spinner while jobs are loading - [ ] Analytics page shows a skeleton/spinner while data is loading - [ ] Both pages show a user-friendly error message when the API returns an error or the request fails - [ ] No console errors introduced
AI-Manager added the P2agent-readymediumfeature labels 2026-03-28 17:23:38 +00:00
AI-Manager commented 2026-03-28 18:04:19 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Both Batch and Analytics pages have loading skeletons (animated pulse placeholders) and error states with retry buttons. Batch page shows skeleton cards while jobs load, and a styled error message with retry/dismiss on failure. Analytics page shows skeleton cards and chart placeholders while loading, and a detailed error state with retry button on failure. Empty states are also handled on both pages.

**Resolved.** Both Batch and Analytics pages have loading skeletons (animated pulse placeholders) and error states with retry buttons. Batch page shows skeleton cards while jobs load, and a styled error message with retry/dismiss on failure. Analytics page shows skeleton cards and chart placeholders while loading, and a detailed error state with retry button on failure. Empty states are also handled on both pages.
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#746
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?