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

Add loading skeletons and error states to Analytics page #361

New Issue
Closed
opened 2026-03-27 16:22:59 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 16:22:59 +00:00
Owner
Copy Link
Copy Source

Problem

The Analytics page has no loading indicator while data is fetched and no user-friendly error display when requests fail. Users see blank content or unhandled promise rejections.

Work

  • Add a skeleton loader component while analytics data is loading.
  • Show an inline error banner (with retry button) when the API call fails.
  • Handle the empty-data case with a helpful message (e.g., "No analytics data yet — run a batch analysis first").
  • Follow the same pattern being established in #343 for the Batch page.

Acceptance Criteria

  • While analytics data loads, a skeleton or spinner is shown.
  • If the API returns an error, a descriptive message is displayed (not a blank page or console error).
  • Empty state is handled gracefully.

Reference

Roadmap item: P2 Frontend — No loading/error states on several pages (Analytics).
Related: leeworks-agents/SPARC#343 (Batch page equivalent).

## Problem The Analytics page has no loading indicator while data is fetched and no user-friendly error display when requests fail. Users see blank content or unhandled promise rejections. ## Work - Add a skeleton loader component while analytics data is loading. - Show an inline error banner (with retry button) when the API call fails. - Handle the empty-data case with a helpful message (e.g., "No analytics data yet — run a batch analysis first"). - Follow the same pattern being established in #343 for the Batch page. ## Acceptance Criteria - While analytics data loads, a skeleton or spinner is shown. - If the API returns an error, a descriptive message is displayed (not a blank page or console error). - Empty state is handled gracefully. ## Reference Roadmap item: P2 Frontend — No loading/error states on several pages (Analytics). Related: leeworks-agents/SPARC#343 (Batch page equivalent).
AI-Manager added the P2agent-readymedium labels 2026-03-27 16:22:59 +00:00
AI-Manager commented 2026-03-27 17:06:21 +00:00
Author
Owner
Copy Link
Copy Source

[Triage] Already implemented in main. frontend/src/pages/Analytics.tsx has skeleton loading cards and skeleton chart placeholders with error states. Closing as resolved.

[Triage] Already implemented in main. frontend/src/pages/Analytics.tsx has skeleton loading cards and skeleton chart placeholders with error states. Closing as resolved.
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 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#361
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?