stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Open Web Push digests in the mobile Updates inbox #647

New Issue
Closed
opened 2026-08-12 11:52:55 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 11:52:55 +00:00
Owner
Copy Link

Problem

Web Push digest notifications already navigate to #/my-work/updates, but the dashboard work-route parser rejects that queue-level route as unavailable. A mobile operator tapping a digest is therefore removed from the promised Updates triage flow.

Scope

Recognize the canonical Updates inbox route, select/focus that queue after hydration, preserve it while opening update details, and return to it with browser Back/close. Keep empty/offline inbox states valid.

Acceptance criteria

  • Cold and existing-client launches at #/my-work/updates select the Updates filter without a route-unavailable message.
  • Opening an update uses its detail hash; Back/close restores the Updates route and queue focus.
  • Empty Updates remains a valid route.
  • Existing push and mobile behavior tests pass, with strict route behavior covered first.

Evidence: frontend/service-worker.js emits this route while frontend/work-route.js only accepts detail routes. Historical issue-title and recent-commit review found no prior fix.

## Problem Web Push digest notifications already navigate to `#/my-work/updates`, but the dashboard work-route parser rejects that queue-level route as unavailable. A mobile operator tapping a digest is therefore removed from the promised Updates triage flow. ## Scope Recognize the canonical Updates inbox route, select/focus that queue after hydration, preserve it while opening update details, and return to it with browser Back/close. Keep empty/offline inbox states valid. ## Acceptance criteria - Cold and existing-client launches at `#/my-work/updates` select the Updates filter without a route-unavailable message. - Opening an update uses its detail hash; Back/close restores the Updates route and queue focus. - Empty Updates remains a valid route. - Existing push and mobile behavior tests pass, with strict route behavior covered first. Evidence: `frontend/service-worker.js` emits this route while `frontend/work-route.js` only accepts detail routes. Historical issue-title and recent-commit review found no prior fix.
timmy self-assigned this 2026-08-12 11:52:55 +00:00
timmy closed this issue 2026-08-12 12:04:41 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#647
No description provided.
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?