"Consider adding soft-delete support"

[simonforsberg]

CodeRabbit suggestion/nitpick comment on Ticket entity:

"Removing cascade operations aligns with the requirement to preserve whistleblower data.

However, without cascade and without explicit ON DELETE constraints at the DB level, attempting to delete a Ticket will either:

• Fail with a FK constraint violation (desired behavior), or
• Leave orphaned TicketComment, Attachment, and AuditLog rows if FK constraints aren't enforced

To ensure data integrity, consider implementing a soft-delete pattern (e.g., an isDeleted or deletedAt field) and preventing hard deletes at the service layer. This makes the intent explicit and avoids relying solely on DB constraint behavior.

[coderabbitai]

🔗 Related PRs

#1 - Feature/entities [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!