Skip to content

✨ Notify reporters of report status (LK-C07) - #136

Merged
Logan2234 merged 2 commits into
mainfrom
feature/lk-c07-report-notifications
Aug 26, 2026
Merged

✨ Notify reporters of report status (LK-C07)#136
Logan2234 merged 2 commits into
mainfrom
feature/lk-c07-report-notifications

Conversation

@Logan2234

@Logan2234 Logan2234 commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • DSA art. 16(4): receipt confirmation is the caller's own success toast on submission (already in place, e.g. CommentThread.svelte) — no backend acknowledgment needed.
  • DSA art. 16(5): reporter gets an in-app notification (NotificationType.REPORT_RESOLVED) once their report is resolved or dismissed, via ReportService.resolve() (covers both the plain resolve and the take-down path). Deliberately generic — no detail on any measure taken against the reported content's author, which that user gets separately via ModerationDecisionService (LK-C01).
  • Non-registered-third-party reporting channel required by the ticket is already covered by CGU §9 "Notification d'un contenu illicite" (LK-C10) — no change needed there.

Closes https://github.com/Logan2234/loomkeep-roadmap/issues/11

Test plan

  • pnpm --filter @loomkeep/api exec jest src/reports src/mail — new/updated unit tests green
  • pnpm --filter @loomkeep/api exec jest — full API suite green (737 tests)
  • pnpm --filter @loomkeep/api exec tsc --noEmit — clean
  • pnpm --filter @loomkeep/web check — clean

DSA art. 16(4)/16(5): a reporter now gets an acknowledgment (email +
in-app) when they file a report, and a follow-up notice once it's
resolved or dismissed — deliberately generic on the resolution side,
since the detailed statement of reasons for any measure taken already
goes to the sanctioned user via ModerationDecisionService (LK-C01).

The non-registered-third-party reporting channel required by the same
ticket is already covered by the CGU §9 "Notification d'un contenu
illicite" section (LK-C10) — no further change needed there.
Simpler than the first pass: DSA art. 16(4)'s receipt confirmation is
already the caller's own success toast on submission (e.g.
CommentThread.svelte) — nothing beats that for "without undue delay",
so no backend acknowledgment (email or in-app) is needed at all.
Art. 16(5)'s resolution notice doesn't mandate a specific channel
either, so it's in-app only now, no email — same channel the report
was filed through.
@github-actions github-actions Bot added api apps/api (NestJS) shared packages/shared labels Aug 26, 2026
@Logan2234
Logan2234 merged commit fe74999 into main Aug 26, 2026
15 of 16 checks passed
@Logan2234
Logan2234 deleted the feature/lk-c07-report-notifications branch August 26, 2026 11:48
@Logan2234 Logan2234 changed the title Notify reporters of report status (LK-C07) ✨ Notify reporters of report status (LK-C07) Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api apps/api (NestJS) shared packages/shared

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant