milestone-sse: wire publish at all milestone-count mutation sites #11

Closed
opened 2026-05-16 00:16:09 +03:00 by oleks · 0 comments
Owner

Insert publish calls at the choke points from Issue A so every milestone-count change emits an event regardless of entry point (web or REST):

  • issue close / reopen (when the issue has a milestone)
  • issue assigned to / removed from a milestone (denominator change)
  • issue deletion (when it had a milestone)
  • milestone create / edit / close / delete

Prefer model/service choke points over per-handler insertion. Use go Publish… so handlers stay responsive.

Blocked by Issue B.

Insert publish calls at the choke points from Issue A so every milestone-count change emits an event regardless of entry point (web or REST): - issue close / reopen (when the issue has a milestone) - issue assigned to / removed from a milestone (denominator change) - issue deletion (when it had a milestone) - milestone create / edit / close / delete Prefer model/service choke points over per-handler insertion. Use `go Publish…` so handlers stay responsive. Blocked by Issue B.
oleks added this to the Milestone progress SSE — live-updating progress bars milestone 2026-05-16 00:16:09 +03:00
oleks added this to the (deleted) project 2026-05-16 00:16:23 +03:00
oleks added the area/milestone-ssekind/backend labels 2026-05-16 00:20:47 +03:00
oleks added this to the Milestone SSE project 2026-05-16 00:22:12 +03:00
oleks moved this to In Progress in Milestone SSE on 2026-05-16 00:29:26 +03:00
oleks moved this to Done in Milestone SSE on 2026-05-16 10:40:49 +03:00
oleks closed this issue 2026-05-16 14:24:19 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oleks/gitea#11