✨ Notify reporters of report status (LK-C07) - #136
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CommentThread.svelte) — no backend acknowledgment needed.NotificationType.REPORT_RESOLVED) once their report is resolved or dismissed, viaReportService.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 viaModerationDecisionService(LK-C01).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 greenpnpm --filter @loomkeep/api exec jest— full API suite green (737 tests)pnpm --filter @loomkeep/api exec tsc --noEmit— cleanpnpm --filter @loomkeep/web check— clean