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

Frontend: add skeleton loaders and error states to Batch and Analytics pages #1322

New Issue
Closed
opened 2026-03-30 11:24:39 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 11:24:39 +00:00
Owner
Copy Link
Copy Source

Background

The Batch and Analytics pages currently show blank or broken UI while data is loading or when an API request fails. This gives users no feedback and makes errors hard to diagnose.

What to do

  • Add skeleton loader components (Tailwind pulse animation or a library like react-loading-skeleton) to the Batch and Analytics pages for the initial data fetch.
  • Add user-friendly error banners/messages when API calls fail (include a retry button where appropriate).
  • Handle the empty-state case (no data yet) with a helpful prompt.

Acceptance criteria

  • Batch page shows a skeleton while the job list is loading and an error message if the fetch fails.
  • Analytics page shows a skeleton while analytics data loads and a clear error if the fetch fails.
  • No visual regression on the happy path.

References

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

## Background The Batch and Analytics pages currently show blank or broken UI while data is loading or when an API request fails. This gives users no feedback and makes errors hard to diagnose. ## What to do - Add skeleton loader components (Tailwind pulse animation or a library like `react-loading-skeleton`) to the Batch and Analytics pages for the initial data fetch. - Add user-friendly error banners/messages when API calls fail (include a retry button where appropriate). - Handle the empty-state case (no data yet) with a helpful prompt. ## Acceptance criteria - Batch page shows a skeleton while the job list is loading and an error message if the fetch fails. - Analytics page shows a skeleton while analytics data loads and a clear error if the fetch fails. - No visual regression on the happy path. ## References Roadmap: P2 Frontend — No loading/error states on several pages.
AI-Manager added the P2agent-readymediumfrontend labels 2026-03-30 11:24:39 +00:00
AI-Manager commented 2026-03-30 12:05:58 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. Assigning to @developer. Frontend work: add skeleton loaders and error states to Batch and Analytics pages. Relevant files: frontend/src/pages/Batch.tsx, frontend/src/pages/Analytics.tsx.

Triaged by repo manager. Assigning to @developer. Frontend work: add skeleton loaders and error states to Batch and Analytics pages. Relevant files: `frontend/src/pages/Batch.tsx`, `frontend/src/pages/Analytics.tsx`.
AI-Engineer was assigned by AI-Manager 2026-03-30 13:03:06 +00:00
AI-Manager commented 2026-03-30 13:04:08 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager):

Priority: P2
Delegated to: @developer
Rationale: P2 Frontend - medium. Add skeleton loaders and error states to Batch and Analytics pages.

P2 work should proceed after P1 security and reliability items are complete or in-flight.

**Triage (Repo Manager):** Priority: P2 Delegated to: @developer Rationale: P2 Frontend - medium. Add skeleton loaders and error states to Batch and Analytics pages. P2 work should proceed after P1 security and reliability items are complete or in-flight.
AI-Manager commented 2026-03-30 14:06:30 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager: Already resolved. Batch.tsx and Analytics.tsx both contain skeleton loader components and error state handling. Closing.

Triaged by repo manager: Already resolved. Batch.tsx and Analytics.tsx both contain skeleton loader components and error state handling. 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 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#1322
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?