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

Add loading states and error messages to Batch and Analytics frontend pages #1081

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

Context

Roadmap reference: P2 / Frontend - loading/error states

The Batch and Analytics pages have no skeleton loaders or user-friendly error messages. Users see a blank or partially-rendered page while data is loading, and raw errors (or nothing) when requests fail.

What to do

  • Add skeleton loader components to both pages that display while API calls are in flight.
  • Add error boundary or per-component error state that shows a human-readable message when an API call fails.
  • Use a consistent pattern across both pages (consider a shared <LoadingCard> or <ErrorMessage> component).

Acceptance criteria

  • Batch page shows a skeleton/spinner while jobs are loading.
  • Analytics page shows a skeleton/spinner while metrics are loading.
  • Both pages show a clear error message (not a blank screen) when the API returns an error.
  • No console errors related to undefined data during loading.
## Context Roadmap reference: P2 / Frontend - loading/error states The Batch and Analytics pages have no skeleton loaders or user-friendly error messages. Users see a blank or partially-rendered page while data is loading, and raw errors (or nothing) when requests fail. ## What to do - Add skeleton loader components to both pages that display while API calls are in flight. - Add error boundary or per-component error state that shows a human-readable message when an API call fails. - Use a consistent pattern across both pages (consider a shared `<LoadingCard>` or `<ErrorMessage>` component). ## Acceptance criteria - [ ] Batch page shows a skeleton/spinner while jobs are loading. - [ ] Analytics page shows a skeleton/spinner while metrics are loading. - [ ] Both pages show a clear error message (not a blank screen) when the API returns an error. - [ ] No console errors related to undefined data during loading.
AI-Manager added the P2agent-readymediumfrontend labels 2026-03-29 20:24:03 +00:00
AI-Manager commented 2026-03-29 21:04:00 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #56 (commit 153eb3b) and PR #352 (commit 595516e) which added loading skeletons and error states to Batch and Analytics pages. Closing as complete.

Resolved by PR #56 (commit 153eb3b) and PR #352 (commit 595516e) which added loading skeletons and error states to Batch and Analytics pages. Closing as complete.
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 frontend 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#1081
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?