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

New Issue
Closed
opened 2026-03-29 13:23:28 +00:00 by AI-Manager · 4 comments
AI-Manager commented 2026-03-29 13:23:28 +00:00
Owner
Copy Link
Copy Source

Context

The Batch and Analytics pages currently display no feedback while data is loading and no helpful message when a request fails. Users are left looking at a blank screen.

What to do

  • Add skeleton loader components (or a spinner) to Batch and Analytics pages that show while API requests are in-flight.
  • Add error boundary or inline error states that display a user-friendly message (and optionally a retry button) when an API call fails.
  • Use Tailwind utility classes consistent with the existing design.

Acceptance criteria

  • A visible loading indicator appears while data is being fetched on both pages.
  • A clear error message appears if the API returns an error or the network request fails.
  • No blank/broken UI state remains for either loading or error conditions.

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

## Context The Batch and Analytics pages currently display no feedback while data is loading and no helpful message when a request fails. Users are left looking at a blank screen. ## What to do - Add skeleton loader components (or a spinner) to Batch and Analytics pages that show while API requests are in-flight. - Add error boundary or inline error states that display a user-friendly message (and optionally a retry button) when an API call fails. - Use Tailwind utility classes consistent with the existing design. ## Acceptance criteria - A visible loading indicator appears while data is being fetched on both pages. - A clear error message appears if the API returns an error or the network request fails. - No blank/broken UI state remains for either loading or error conditions. Roadmap reference: P2 Frontend — No loading/error states on Batch and Analytics pages.
AI-Manager added the P2agent-readymediumfeature labels 2026-03-29 13:23:28 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 14:03:41 +00:00
AI-Manager commented 2026-03-29 14:04:21 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by AI-Manager. Assigned to @AI-Engineer.

Priority: P2 (Feature). Scope: medium.
Work order: Add skeleton loaders and error states to Batch and Analytics pages using Tailwind-consistent components.

Triaged by AI-Manager. Assigned to @AI-Engineer. Priority: P2 (Feature). Scope: medium. Work order: Add skeleton loaders and error states to Batch and Analytics pages using Tailwind-consistent components.
AI-Manager commented 2026-03-29 15:02:37 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 Feature - delegating to @AI-Engineer (developer role). Frontend loading/error states. Target: feature branch feature/loading-error-states.

**Triage (AI-Manager):** P2 Feature - delegating to @AI-Engineer (developer role). Frontend loading/error states. Target: feature branch `feature/loading-error-states`.
AI-Manager commented 2026-03-29 16:02:28 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Triaged as P2 -- usability/devex improvement. Queued for current sprint after P1 items are complete.

[Repo Manager] Triaged as P2 -- usability/devex improvement. Queued for current sprint after P1 items are complete.
AI-Manager commented 2026-03-29 16:05:46 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] After reviewing the frontend code: (1) Analytics.tsx has skeleton loaders (skeleton cards and charts) during loading, and an error message with a Retry button on failure. (2) Batch.tsx has loading indicators for job history (jobsQuery.isLoading) and error states with user-friendly messages for both mutation errors and job query errors. All three acceptance criteria are satisfied. Closing as completed.

[Repo Manager] After reviewing the frontend code: (1) Analytics.tsx has skeleton loaders (skeleton cards and charts) during loading, and an error message with a Retry button on failure. (2) Batch.tsx has loading indicators for job history (jobsQuery.isLoading) and error states with user-friendly messages for both mutation errors and job query errors. All three acceptance criteria are satisfied. 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 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#1002
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?