Skip to content

Feature: Implement Feedback Loop for Missed Redactions #5

@matthewgoluba

Description

@matthewgoluba

To support a community-driven improvement cycle, users need a way to report when the tool misses sensitive data.

Architecture:

  • Bun HTTP server endpoint (part of packages/api/)
  • PostgreSQL database for persistent storage (local dev + production)
  • No external services - all self-hosted

Requirements:

  • Endpoint: POST /api/feedback
  • Payload: { original: string, missed: string, type?: string, regex?: string, sampleData?: string, patternName?: string, category?: string }
  • Storage: PostgreSQL database
  • Admin: GET /api/feedback to list all submissions

Tasks:

  • Add PostgreSQL connection to API server
  • Create feedback table schema
  • Create POST /api/feedback route handler
  • Create GET /api/feedback route handler (admin view)
  • Add database migration script
  • Document environment variables for DB connection

Metadata

Metadata

Assignees

Labels

apiREST API relatedcoreCore library functionalityenhancementNew feature or request

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions