Problem reports on guides, with optional email to the owner (#99) #148
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!148
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/99-problem-reports"
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?
Closes #99.
X-Forwarded-Forentry)/reports: admins see all reports, authors those on guides they may edit; Open/Resolved tabs, "Mark as resolved" records who and when. Badge with open reports in the admin menu (admins) and the user menu (authors). Guests get a 404AUTH_SECRET, never sent back to the browser; after a restore with anotherAUTH_SECRETthe settings ask for it againProblemReportmodel and migration;/reportsis now a reserved address (changelog)Dependency:
nodemailer10.3.1. It makes npm nest@auth/coreundernext-auth, so the JWT type augmentation insrc/auth/auth.tsnow targetsnext-auth/jwt.Tests: unit tests for report validation, rate limiter, recipients and email text, older backups, password sealing, the SMTP form and transport options;
e2e/problemReports.spec.tsfor the report flow and permissions,e2e/settings.spec.tsfor the email settings and a failing test email. Typecheck, lint, 610/610 unit, 90/90 e2e, handbookzensical build --strictclean.After merging: restart the dev server (new migration, Prisma client, dependency).
🤖 Generated with Claude Code