Skip to content

fix(ui): scope processings notifications by department#108

Draft
BatLeDev wants to merge 1 commit into
masterfrom
fix-notifications-department
Draft

fix(ui): scope processings notifications by department#108
BatLeDev wants to merge 1 commit into
masterfrom
fix-notifications-department

Conversation

@BatLeDev

Copy link
Copy Markdown
Member

The processings-list notification subscription (processings-actions.vue) passed no sender, so it matched no events — every processings event is published with a sender (run.owner/processing.owner). It now builds a sender scoped to the current account:

  • root org account → organization:id:* to receive events from every department of the org (root + departments)
  • department-scoped account → organization:id:department, avoiding cross-department leakage
  • personal account → user:id (no wildcard)

The sender is repeated per topic since events' embed/subscribe.vue maps senders[i] to topic i.

Why: mirror the reuse-submit notification fix made in data-fair/portals, following the :* wildcard support added in the events service (work item 61). The per-processing subscription (processing-actions.vue) already carries the owner's concrete department and is unchanged.

Heads-up: behavior change — the list previously received no notifications and now does. The :* wildcard relies on the events service support being deployed.

The processings-list notification subscription passed no sender, so it
matched no events (every processings event is published with a sender).
Root org accounts now subscribe with :* to receive events from every
department of the org (root + departments), while a department-scoped
account only subscribes to its own department, avoiding cross-department
leakage. This mirrors the reuse-submit fix in data-fair/portals and
relies on the :* wildcard support added in the events service.
@github-actions github-actions Bot added the fix label Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant