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

Feature: Add loading states and error messages to Batch and Analytics pages #722

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

Summary

The Batch and Analytics pages in the React frontend render content immediately without handling loading or error states. Users see blank content or unhandled exceptions when API calls are slow or fail.

What to do

  • Add skeleton loaders (or spinner components) to the Batch and Analytics pages while data is being fetched.
  • Add user-friendly error message banners when API calls fail, including a retry action where appropriate.
  • Use Tanstack Query error/loading states (or equivalent) consistently across both pages.

Acceptance Criteria

  • A visible loading indicator is shown while API data loads on both pages.
  • A clear error message is displayed (not a blank screen or console error) when an API call fails.
  • Dismissing or retrying the error works correctly.
  • No regressions on other pages.

Reference

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

## Summary The Batch and Analytics pages in the React frontend render content immediately without handling loading or error states. Users see blank content or unhandled exceptions when API calls are slow or fail. ## What to do - Add skeleton loaders (or spinner components) to the Batch and Analytics pages while data is being fetched. - Add user-friendly error message banners when API calls fail, including a retry action where appropriate. - Use Tanstack Query error/loading states (or equivalent) consistently across both pages. ## Acceptance Criteria - [ ] A visible loading indicator is shown while API data loads on both pages. - [ ] A clear error message is displayed (not a blank screen or console error) when an API call fails. - [ ] Dismissing or retrying the error works correctly. - [ ] No regressions on other pages. ## Reference Roadmap: P2 Frontend — No loading/error states on several pages.
AI-Manager added the P2agent-readymediumfeature labels 2026-03-28 16:23:31 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 17:03:17 +00:00
AI-Manager commented 2026-03-28 17:06:00 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. Both Batch.tsx and Analytics.tsx have skeleton loaders and error states with AlertCircle icons.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. Both Batch.tsx and Analytics.tsx have skeleton loaders and error states with AlertCircle icons. Closing as already implemented in the codebase.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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