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

React to conversation comments without leaving mobile work #1380

New Issue
Closed
opened 2026-08-25 04:53:15 +00:00 by timmy · 0 comments
timmy commented 2026-08-25 04:53:15 +00:00
Owner
Copy Link

Problem

Operators can only react while acknowledging the newest unread notification. Ordinary issue, pull-request, and Updates comments require leaving Stackchain or posting a noisy reply.

Evidence and non-duplication

Current shared renderer (frontend/dashboard.js, frontend/comment-actions.js) exposes comment bodies plus owned Edit/Delete only. Gitea reaction plumbing exists solely in acknowledge_notification, hard-coded to +1 and coupled to marking the thread read (#539). A scan of all 693 historical issue titles, 683 pull titles, current open work, releases, and recent commits found no reversible in-context comment reaction flow.

Acceptance

  • A React control is available on loaded issue, pull-request, and Updates comments.
  • Opening it loads authoritative Gitea reaction counts and the current operator selection without changing read state.
  • Operators can add an allowed reaction or remove their selected reaction; the response is confirmed from Gitea.
  • Mutations are bound to the visible repository/item/comment or notification conversation and fail closed on mismatch.
  • Offline mode leaves comments readable and says Reconnect to react. without mutation.
  • At 320px controls wrap without horizontal overflow and touch targets are at least 44px.
  • Focus returns to the trigger after selection/cancel; rapid taps are single-flight.
  • Behavioral backend/frontend tests and the full suite pass.
## Problem Operators can only react while acknowledging the newest unread notification. Ordinary issue, pull-request, and Updates comments require leaving Stackchain or posting a noisy reply. ## Evidence and non-duplication Current shared renderer (`frontend/dashboard.js`, `frontend/comment-actions.js`) exposes comment bodies plus owned Edit/Delete only. Gitea reaction plumbing exists solely in `acknowledge_notification`, hard-coded to `+1` and coupled to marking the thread read (#539). A scan of all 693 historical issue titles, 683 pull titles, current open work, releases, and recent commits found no reversible in-context comment reaction flow. ## Acceptance - A React control is available on loaded issue, pull-request, and Updates comments. - Opening it loads authoritative Gitea reaction counts and the current operator selection without changing read state. - Operators can add an allowed reaction or remove their selected reaction; the response is confirmed from Gitea. - Mutations are bound to the visible repository/item/comment or notification conversation and fail closed on mismatch. - Offline mode leaves comments readable and says `Reconnect to react.` without mutation. - At 320px controls wrap without horizontal overflow and touch targets are at least 44px. - Focus returns to the trigger after selection/cancel; rapid taps are single-flight. - Behavioral backend/frontend tests and the full suite pass.
timmy self-assigned this 2026-08-25 04:53:15 +00:00
timmy closed this issue 2026-08-25 05:21:14 +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#1380
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?