Skip to content

feat: add loading skeleton distinct from not-found state to stream details page (Closes #1088) - #1155

Open
sojetunde8 wants to merge 1 commit into
LabsCrypt:mainfrom
sojetunde8:fix/issue-1088-loading-skeleton-stream-details
Open

feat: add loading skeleton distinct from not-found state to stream details page (Closes #1088)#1155
sojetunde8 wants to merge 1 commit into
LabsCrypt:mainfrom
sojetunde8:fix/issue-1088-loading-skeleton-stream-details

Conversation

@sojetunde8

Copy link
Copy Markdown

Closes #1088

Summary

  • Replace the minimal spinner loading state with a full-page skeleton UI that mimics the stream details layout: header, overview, stats cards, progress bar, action buttons, and event history
  • Each skeleton element uses animate-pulse shimmer placeholders styled to match the dark theme
  • The not-found/error state remains visually distinct with a red AlertTriangle icon — no risk of confusing the two states
  • Loading region has proper role="status" and aria-label for accessibility

Testing

  • Added 4 unit tests covering: skeleton renders while fetch is in-flight, transition from skeleton to content on success, transition from skeleton to not-found on 404, and error message display on API failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Frontend] stream-details-content.tsx has no loading skeleton distinct from the not-found state, so both render the same blank layout briefly

1 participant