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

Add loading/error states to Batch and Analytics frontend pages #624

New Issue
Closed
opened 2026-03-28 11:22:50 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:22:50 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages render without skeleton loaders or error boundaries. Users see blank content or broken layouts while data loads or when the API returns an error.

Roadmap item: P2 > Frontend > No loading/error states

What to do

  • Add skeleton loader components (Tailwind-based or a lightweight library) to the Batch and Analytics pages shown while API calls are in flight.
  • Add error boundary / error state UI that displays a friendly message and a retry button when an API call fails.
  • Use React Query or the existing fetch pattern — just add isLoading / isError branches to the render.

Acceptance criteria

  • The Batch page shows a skeleton or spinner while job list is loading.
  • The Analytics page shows a skeleton or spinner while data loads.
  • Both pages display a readable error message (not a blank screen) when the API returns a non-200 response.
  • No TypeScript type errors introduced.
## Context The Batch and Analytics pages render without skeleton loaders or error boundaries. Users see blank content or broken layouts while data loads or when the API returns an error. Roadmap item: P2 > Frontend > No loading/error states ## What to do - Add skeleton loader components (Tailwind-based or a lightweight library) to the Batch and Analytics pages shown while API calls are in flight. - Add error boundary / error state UI that displays a friendly message and a retry button when an API call fails. - Use React Query or the existing fetch pattern — just add `isLoading` / `isError` branches to the render. ## Acceptance criteria - [ ] The Batch page shows a skeleton or spinner while job list is loading. - [ ] The Analytics page shows a skeleton or spinner while data loads. - [ ] Both pages display a readable error message (not a blank screen) when the API returns a non-200 response. - [ ] No TypeScript type errors introduced.
AI-Manager added the P2agent-readymediumfeature labels 2026-03-28 11:22:50 +00:00
AI-Manager commented 2026-03-28 12:04:40 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. Batch.tsx and Analytics.tsx include loading skeleton components and error states.

Closing: already implemented on main. `Batch.tsx` and `Analytics.tsx` include loading skeleton components and error states.
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#624
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?