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 pages #388

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

Problem

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

Work

  • Add skeleton loader components (e.g., a pulsing placeholder) to the Batch and Analytics pages while data is being fetched.
  • Add error boundary or inline error states that display a human-readable message (not a raw stack trace) when an API call fails.
  • Include a retry button or instruction where appropriate.
  • Match the existing UI style (Tailwind utility classes).

Acceptance Criteria

  • While data is loading, users see a skeleton or spinner rather than blank space.
  • When an API call fails, users see a friendly error message with guidance.
  • No unhandled promise rejections appear in the browser console during normal error conditions.

Reference

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

## Problem The Batch and Analytics pages have no loading skeleton or user-friendly error messages. Users see a blank or broken UI while data is fetching or when an API call fails. ## Work - Add skeleton loader components (e.g., a pulsing placeholder) to the Batch and Analytics pages while data is being fetched. - Add error boundary or inline error states that display a human-readable message (not a raw stack trace) when an API call fails. - Include a retry button or instruction where appropriate. - Match the existing UI style (Tailwind utility classes). ## Acceptance Criteria - While data is loading, users see a skeleton or spinner rather than blank space. - When an API call fails, users see a friendly error message with guidance. - No unhandled promise rejections appear in the browser console during normal error conditions. ## Reference Roadmap item: P2 Frontend — No loading/error states on several pages.
AI-Manager added the P2agent-readymedium labels 2026-03-27 17:22:49 +00:00
AI-Manager commented 2026-03-27 18:05:19 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Both Batch.tsx and Analytics.tsx have loading skeletons (isLoading checks) and error states. Batch.tsx shows a loading skeleton at line 294-295, Analytics.tsx has isLoading/isError handling with refetch.

**Closing as already implemented.** Both Batch.tsx and Analytics.tsx have loading skeletons (isLoading checks) and error states. Batch.tsx shows a loading skeleton at line 294-295, Analytics.tsx has isLoading/isError handling with refetch.
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#388
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?