Skip to content

fix(governance): namespace flags by content type to prevent id collisions - #419

Merged
3m1n3nc3 merged 1 commit into
geevapp:mainfrom
Copstud3:fix/governance-flag-namespacing
Jul 28, 2026
Merged

fix(governance): namespace flags by content type to prevent id collisions#419
3m1n3nc3 merged 1 commit into
geevapp:mainfrom
Copstud3:fix/governance-flag-namespacing

Conversation

@Copstud3

@Copstud3 Copstud3 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Description

Namespaces governance flags by content type so giveaways and help requests with the same numeric ID cannot share flag records, counts, or auto-suspension behavior.

  • Adds a ContentType enum for giveaways and help requests
  • Keys flag records and counts by content type and target ID
  • Requires content type in flagging and query APIs
  • Resolves auto-suspension against only the intended content type
  • Adds regression coverage for same-ID coexistence

Closes #411

Checklist

  • I have tested my changes locally
  • I have updated documentation as needed
  • Prisma generation is not applicable
  • Prisma migration is not applicable

Testing

  • cargo test - 73 passed, 0 failed
  • cargo fmt -- --check

@3m1n3nc3
3m1n3nc3 merged commit 3812019 into geevapp:main Jul 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Governance] Separate flag records by content type to prevent ID collisions

2 participants