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

Edit or delete your own conversation comments #575

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

User problem

Mobile operators can read, reply, and attach screenshots inside issue, pull-request, and unread-update sheets, but cannot correct or retract a comment they just posted without leaving Stackchain for Gitea. This loses focused Today context and makes accidental or sensitive posts costly.

Evidence

  • frontend/dashboard.js renders comment author/time/body with no owned-comment actions.
  • src/gitea_proxy.py and src/main.py expose comment creation only.
  • Existing normalized comments already carry stable comment IDs and authors.
  • Gitea supports PATCH/DELETE on /repos/{owner}/{repo}/issues/comments/{id}.
  • No historical issue/PR/commit title covers editing or deleting posted comments; adjacent #189 edits issue title/body and #503 creates replies.

Acceptance criteria

  • Owned comments in issue, pull, and unread-update conversations expose mobile-sized Edit and Delete actions; other authors’ comments do not.
  • Edit is inline, preserves exact Markdown on failure/cancel, and rerenders the authoritative returned comment without closing the sheet or losing pagination/draft state.
  • Delete requires confirmation and removes only the deleted comment without advancing Today or changing unread state.
  • Server verifies enclosing thread access and comment ownership before upstream mutation; forged/cross-thread/other-author IDs cause no PATCH/DELETE.
  • Offline/failure states never claim success and preserve recoverable edit text.
  • Behavioral backend/frontend tests cover ownership, successful mutation, rejection, and all three conversation entry points; rendered mobile layout has no horizontal overflow and touch targets are at least 44px.
## User problem Mobile operators can read, reply, and attach screenshots inside issue, pull-request, and unread-update sheets, but cannot correct or retract a comment they just posted without leaving Stackchain for Gitea. This loses focused Today context and makes accidental or sensitive posts costly. ## Evidence - `frontend/dashboard.js` renders comment author/time/body with no owned-comment actions. - `src/gitea_proxy.py` and `src/main.py` expose comment creation only. - Existing normalized comments already carry stable comment IDs and authors. - Gitea supports PATCH/DELETE on `/repos/{owner}/{repo}/issues/comments/{id}`. - No historical issue/PR/commit title covers editing or deleting posted comments; adjacent #189 edits issue title/body and #503 creates replies. ## Acceptance criteria - Owned comments in issue, pull, and unread-update conversations expose mobile-sized Edit and Delete actions; other authors’ comments do not. - Edit is inline, preserves exact Markdown on failure/cancel, and rerenders the authoritative returned comment without closing the sheet or losing pagination/draft state. - Delete requires confirmation and removes only the deleted comment without advancing Today or changing unread state. - Server verifies enclosing thread access and comment ownership before upstream mutation; forged/cross-thread/other-author IDs cause no PATCH/DELETE. - Offline/failure states never claim success and preserve recoverable edit text. - Behavioral backend/frontend tests cover ownership, successful mutation, rejection, and all three conversation entry points; rendered mobile layout has no horizontal overflow and touch targets are at least 44px.
timmy self-assigned this 2026-08-11 14:55:11 +00:00
timmy closed this issue 2026-08-11 15:23:17 +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#575
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?