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

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

Context

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

The Batch and Analytics pages currently show no feedback while data is loading and no user-friendly message when a request fails. This leads to a blank or stale UI during slow network conditions or API errors.

What to do

  • Add skeleton loaders (or a spinner) to both pages while async data is being fetched.
  • Add an error boundary or inline error message component that shows a human-readable message (and optionally a retry button) when the API returns an error.
  • Reuse any existing loading/error components from the codebase; create shared ones if none exist.

Acceptance criteria

  • The Batch page shows a skeleton/spinner while jobs are loading and an error state if the API call fails.
  • The Analytics page shows a skeleton/spinner while analytics data is loading and an error state on failure.
  • No blank white screen appears during loading or on error.
## Context Roadmap item: P2 -- Frontend -- No loading/error states on several pages The Batch and Analytics pages currently show no feedback while data is loading and no user-friendly message when a request fails. This leads to a blank or stale UI during slow network conditions or API errors. ## What to do - Add skeleton loaders (or a spinner) to both pages while async data is being fetched. - Add an error boundary or inline error message component that shows a human-readable message (and optionally a retry button) when the API returns an error. - Reuse any existing loading/error components from the codebase; create shared ones if none exist. ## Acceptance criteria - [ ] The Batch page shows a skeleton/spinner while jobs are loading and an error state if the API call fails. - [ ] The Analytics page shows a skeleton/spinner while analytics data is loading and an error state on failure. - [ ] No blank white screen appears during loading or on error.
AI-Manager added the P2agent-readymediumfrontend labels 2026-03-30 18:23:27 +00:00
AI-Manager commented 2026-03-30 19:05:29 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already resolved in main.

Both Batch.tsx and Analytics.tsx already have loading states and error handling:

  • Batch.tsx: Uses jobsQuery.isLoading for skeleton loading UI, displays mutation.error.message and jobsQuery.error.message for errors.
  • Analytics.tsx: Uses isLoading state with skeleton cards and charts, has isError handling with error display.

Closing as complete.

**Triage: Already resolved in main.** Both `Batch.tsx` and `Analytics.tsx` already have loading states and error handling: - `Batch.tsx`: Uses `jobsQuery.isLoading` for skeleton loading UI, displays `mutation.error.message` and `jobsQuery.error.message` for errors. - `Analytics.tsx`: Uses `isLoading` state with skeleton cards and charts, has `isError` handling with error display. 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#1412
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?