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

New Issue
Closed
opened 2026-03-30 09:23:57 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 09:23:57 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages make async API calls but show no loading indicator or error message while waiting or when requests fail. This creates a confusing user experience.

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

What to do

  • Add skeleton loaders (or spinner components) while data is being fetched on both pages.
  • Add user-friendly error banners / inline messages when API calls fail (network error, 4xx, 5xx).
  • Use the existing Tailwind + component library conventions already in the project.

Acceptance criteria

  • A loading skeleton or spinner is visible between the request start and response.
  • A user-visible error message appears when the API returns an error.
  • The happy path (data loads successfully) is unchanged.
  • No console errors or unhandled promise rejections.
## Context The Batch and Analytics pages make async API calls but show no loading indicator or error message while waiting or when requests fail. This creates a confusing user experience. Roadmap reference: P2 - Frontend: No loading/error states on several pages ## What to do - Add skeleton loaders (or spinner components) while data is being fetched on both pages. - Add user-friendly error banners / inline messages when API calls fail (network error, 4xx, 5xx). - Use the existing Tailwind + component library conventions already in the project. ## Acceptance criteria - A loading skeleton or spinner is visible between the request start and response. - A user-visible error message appears when the API returns an error. - The happy path (data loads successfully) is unchanged. - No console errors or unhandled promise rejections.
AI-Manager added the P2agent-readymediumfrontend labels 2026-03-30 09:23:57 +00:00
AI-Manager commented 2026-03-30 10:05:37 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

Loading and error states are implemented on main:

  • Analytics page (frontend/src/pages/Analytics.tsx): Uses isLoading and isError from useQuery to show loading spinner and error messages.
  • Batch page (frontend/src/pages/Batch.tsx): Shows loading skeleton during submission and error banner with mutation.isError / mutation.error.message.

Closing as completed.

## Triage: Already Implemented Loading and error states are implemented on `main`: - **Analytics page** (`frontend/src/pages/Analytics.tsx`): Uses `isLoading` and `isError` from `useQuery` to show loading spinner and error messages. - **Batch page** (`frontend/src/pages/Batch.tsx`): Shows loading skeleton during submission and error banner with `mutation.isError` / `mutation.error.message`. Closing as completed.
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 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#1277
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?