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

Preserve mobile My Work queue truth through workspace hydration #1403

New Issue
Closed
opened 2026-08-25 17:51:31 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-25 17:51:31 +00:00
Member
Copy Link

Evidence

The progressive mobile My Work surface exposes every queue before optional workspace hydration, but frontend/progressive-my-work.js only understands Review, Updates, Attention, and kind. Filed and My PRs therefore show false empty results, deferred queues claim there is no work before their state is loaded, counts remain zero, and a progressive queue selection is discarded when dashboard.js takes over. No open or closed issue title covers truthful progressive queue semantics or selection handoff; #1401 only introduced progressive rendering.

User outcome

On slow mobile startup, operators can trust visible queue counts and results, receive an honest loading state for queues whose data is not ready, and keep their selected queue when the full workspace hydrates.

Acceptance criteria

  • Progressive Filed and My PRs use the same work-item semantics as the full workspace and display accurate counts.
  • Today, Agenda, Later, and Drafts announce that they are still loading instead of a definitive empty state before their owning stores hydrate.
  • A queue selected during progressive startup remains selected when the full workspace takes over.
  • The progressive controller exposes its selected filter through a bounded handoff API without retaining event listeners after stop.
  • Behavioral unit coverage proves semantics, counts, deferred states, and selection handoff; focused and full suites pass.
  • The packaged mobile release journey remains green.
## Evidence The progressive mobile My Work surface exposes every queue before optional workspace hydration, but `frontend/progressive-my-work.js` only understands Review, Updates, Attention, and `kind`. Filed and My PRs therefore show false empty results, deferred queues claim there is no work before their state is loaded, counts remain zero, and a progressive queue selection is discarded when `dashboard.js` takes over. No open or closed issue title covers truthful progressive queue semantics or selection handoff; #1401 only introduced progressive rendering. ## User outcome On slow mobile startup, operators can trust visible queue counts and results, receive an honest loading state for queues whose data is not ready, and keep their selected queue when the full workspace hydrates. ## Acceptance criteria - Progressive Filed and My PRs use the same work-item semantics as the full workspace and display accurate counts. - Today, Agenda, Later, and Drafts announce that they are still loading instead of a definitive empty state before their owning stores hydrate. - A queue selected during progressive startup remains selected when the full workspace takes over. - The progressive controller exposes its selected filter through a bounded handoff API without retaining event listeners after stop. - Behavioral unit coverage proves semantics, counts, deferred states, and selection handoff; focused and full suites pass. - The packaged mobile release journey remains green.
timmy was assigned by rockachopa 2026-08-25 17:51:31 +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#1403
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?