Repository navigation
fix(frontend): failed upcoming purchases fetch renders as empty state #713
Description
Summary
Home shows "No upcoming scheduled purchases" when the /api/dashboard/upcoming request fails. The request is also not scoped to the selected filter chips.
Where
Reviewed commit b50ca38: frontend/src/dashboard.ts:177,182,214,436-437.
Failure scenario
The upcoming endpoint returns an error. The widget renders the normal empty state, so the user concludes nothing is scheduled when in fact the data failed to load. Separately, the fetch ignores the account/provider chips, so the widget can disagree with the rest of the page. Verified live.
Suggested fix
Render an inline error with a Retry button on failure, and pass the current scope to the request.
Severity
High: a failed load is presented as "nothing scheduled", hiding upcoming spend.
Reviewer ID: UX-05 (usab H5)
Found by the 2026-10-08 review fleet.
Activity
fix(frontend): announce the upcoming error and keep focus on Retry
fix(frontend): upcoming fetch error state, stable service chart colou…
cristim commentedon Oct 20, 2026
#1186 (
aab65a57) fixed the first half: a failed upcoming fetch now shows an inline error with Retry instead of the empty state. Still open: scoping the fetch to the provider/account chips.getUpcomingPurchases(internal/api/handler_dashboard.go) takes no filter parameters and scopes by session only, so this needs backend filter parameters plus the frontend passing the chip state.IAmJSD commentedon Oct 24, 2026
Claiming: working on this
fix(frontend): scope Home upcoming purchases to the provider chip (#1365
fix(api): filter upcoming purchases by the provider and account chips (…
IAmJSD commentedon Oct 28, 2026
Status update (2026-10-28): the backend half merged in #1555:
GET /api/dashboard/upcomingnow acceptsprovider,account_idsandaccount_id, intersected with the session scope.Left: frontend (UI owner):
getUpcomingPurchasesshould send the chip state likegetDashboardSummary, and the "account filter does not apply here" note can go.