Francy51/Neon-Desk
2
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Add actionable loading, empty, and error states to Overview, Financials, and Graphing #7

New Issue
Open
opened 2026-03-14 22:16:28 +00:00 by Francy51 · 0 comments
Francy51 commented 2026-03-14 22:16:28 +00:00
Owner
Copy Link

Summary

Several primary pages do not tell the user what to do next when data is missing, still loading, or unavailable.

Evidence

  • Overview could remain on Loading company overview without an explicit failure mode.
  • Financials showed No rows available, No trend data available, and zeroed normalization values without explaining whether to sync, change ticker, or wait.
  • Graphing opened with a prefilled compare set but still rendered No chart data available, making the default state feel broken.

Expected

  • Users should be able to distinguish loading, empty, and failure states immediately and know the next action.

Acceptance Criteria

  • Each page has distinct states for loading, empty data, and hard failure.
  • Empty states include the next recommended action.
  • Failure states explain the problem in user terms and provide recovery actions.
  • Default routed states do not feel like silent failure when no data is present.
## Summary Several primary pages do not tell the user what to do next when data is missing, still loading, or unavailable. ## Evidence - Overview could remain on `Loading company overview` without an explicit failure mode. - Financials showed `No rows available`, `No trend data available`, and zeroed normalization values without explaining whether to sync, change ticker, or wait. - Graphing opened with a prefilled compare set but still rendered `No chart data available`, making the default state feel broken. ## Expected - Users should be able to distinguish loading, empty, and failure states immediately and know the next action. ## Acceptance Criteria - Each page has distinct states for loading, empty data, and hard failure. - Empty states include the next recommended action. - Failure states explain the problem in user terms and provide recovery actions. - Default routed states do not feel like silent failure when no data is present.
Francy51 added the P2 label 2026-03-14 22:16:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
Critical priority
 P1
High priority
 P2
Medium priority
 P3
Low priority
No Label P2
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
coolify_deployment Francy51
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Francy51/Neon-Desk#7
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?