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

Add loading skeletons and error states to Batch and Analytics pages #80

New Issue
Closed
opened 2026-03-26 14:23:10 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 14:23:10 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics frontend pages have no loading or error states. Users see a blank screen while data loads or when an API call fails, with no feedback.

Work

  • Add skeleton loader components (or Tailwind-based pulse placeholders) to both the Batch and Analytics pages that display while data is being fetched.
  • Add user-friendly error messages (e.g., a banner or inline alert) when API calls fail, including the error reason if available.
  • Handle the empty-state case (no data yet) with a helpful prompt.
  • Ensure these states are covered by component tests or Storybook stories if the project uses them.

Acceptance Criteria

  • Loading state is visible during the API fetch on both pages.
  • If the API returns an error, a readable message is shown instead of a blank or broken UI.
  • Empty state is distinct from loading and error states.

References

Roadmap: Frontend — no loading/error states on several pages.

## Context The Batch and Analytics frontend pages have no loading or error states. Users see a blank screen while data loads or when an API call fails, with no feedback. ## Work - Add skeleton loader components (or Tailwind-based pulse placeholders) to both the Batch and Analytics pages that display while data is being fetched. - Add user-friendly error messages (e.g., a banner or inline alert) when API calls fail, including the error reason if available. - Handle the empty-state case (no data yet) with a helpful prompt. - Ensure these states are covered by component tests or Storybook stories if the project uses them. ## Acceptance Criteria - Loading state is visible during the API fetch on both pages. - If the API returns an error, a readable message is shown instead of a blank or broken UI. - Empty state is distinct from loading and error states. ## References Roadmap: Frontend — no loading/error states on several pages.
AI-Manager added the P2agent-readymedium labels 2026-03-26 14:23:10 +00:00
AI-Manager commented 2026-03-26 15:06:21 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Loading skeletons and error retry states added to Batch and Analytics pages. Implemented in PR #56 (merged). See frontend/src/pages/Batch.tsx and Analytics.tsx.

Resolved. Loading skeletons and error retry states added to Batch and Analytics pages. Implemented in PR #56 (merged). See `frontend/src/pages/Batch.tsx` and `Analytics.tsx`.
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#80
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?