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 #672

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

Context

The Batch and Analytics pages render without any loading indicator while data is being fetched and show no user-friendly message when an API call fails. This leaves users with a blank or broken UI.

What to do

  • Add skeleton loaders (or a spinner) to both pages that display while API requests are in flight.
  • Add an error state that shows a human-readable message (and optionally a retry button) when a request fails.
  • Use the existing Tailwind classes for consistency with the rest of the UI.

Acceptance criteria

  • A skeleton loader is shown on both pages during data fetch.
  • A clear error message is displayed when the API returns an error or the network request fails.
  • A retry button (or equivalent) allows the user to re-fetch without a full page reload.
  • No console errors during the loading and error states.

References

Roadmap item: P2 Frontend — loading/error states on Batch and Analytics pages.

## Context The Batch and Analytics pages render without any loading indicator while data is being fetched and show no user-friendly message when an API call fails. This leaves users with a blank or broken UI. ## What to do - Add skeleton loaders (or a spinner) to both pages that display while API requests are in flight. - Add an error state that shows a human-readable message (and optionally a retry button) when a request fails. - Use the existing Tailwind classes for consistency with the rest of the UI. ## Acceptance criteria - [ ] A skeleton loader is shown on both pages during data fetch. - [ ] A clear error message is displayed when the API returns an error or the network request fails. - [ ] A retry button (or equivalent) allows the user to re-fetch without a full page reload. - [ ] No console errors during the loading and error states. ## References Roadmap item: P2 Frontend — loading/error states on Batch and Analytics pages.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-28 13:23:24 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 14:03:03 +00:00
AI-Manager commented 2026-03-28 15:05:43 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already implemented

This issue has been fully addressed in the fork main branch.

Verification:

  • Both frontend/src/pages/Batch.tsx and frontend/src/pages/Analytics.tsx contain loading skeleton/spinner components.
  • Error states with user-friendly messages are implemented.
  • Merged via PR #56 (feature/loading-error-states) and PR #352 (feature/343-batch-loading-states).

All acceptance criteria are met. Closing.

## Triage: Already implemented This issue has been fully addressed in the fork main branch. **Verification:** - Both `frontend/src/pages/Batch.tsx` and `frontend/src/pages/Analytics.tsx` contain loading skeleton/spinner components. - Error states with user-friendly messages are implemented. - Merged via PR #56 (feature/loading-error-states) and PR #352 (feature/343-batch-loading-states). All acceptance criteria are met. Closing.
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 small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#672
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?