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

Add loading and error states to Batch and Analytics pages #1363

New Issue
Closed
opened 2026-03-30 15:24:16 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 15:24:16 +00:00
Owner
Copy Link
Copy Source

Context

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

The Batch and Analytics pages do not show skeleton loaders while data is fetching, and do not display user-friendly error messages when requests fail.

What to do

  • Add skeleton loader components (using Tailwind animate-pulse or a library) to the Batch and Analytics pages for the loading state.
  • Display an error banner or inline message when API calls return an error, with enough context for the user to understand what went wrong.
  • Ensure error states are dismissible or auto-clear on retry.

Acceptance criteria

  • While data is loading, a skeleton or spinner is visible on both pages.
  • When an API error occurs, a user-readable error message is displayed.
  • No unhandled promise rejections appear in the browser console.
## Context Roadmap item: P2 Frontend - No loading/error states on several pages The Batch and Analytics pages do not show skeleton loaders while data is fetching, and do not display user-friendly error messages when requests fail. ## What to do - Add skeleton loader components (using Tailwind animate-pulse or a library) to the Batch and Analytics pages for the loading state. - Display an error banner or inline message when API calls return an error, with enough context for the user to understand what went wrong. - Ensure error states are dismissible or auto-clear on retry. ## Acceptance criteria - While data is loading, a skeleton or spinner is visible on both pages. - When an API error occurs, a user-readable error message is displayed. - No unhandled promise rejections appear in the browser console.
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-30 15:24:16 +00:00
AI-Manager commented 2026-03-30 16:05:50 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. 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 frontend small
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#1363
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?