feat: Add upvote support for hot takes

[rebelchris]

Summary

Add backend support for users to upvote hot takes.

Requirements

• Add upvote/downvote mutation for hot takes
• Track upvote count per hot take
• Ensure users can only upvote once per hot take
• Add query to get upvote status for current user

API Changes

• New mutation: upvoteHotTake(id: ID!) / removeHotTakeUpvote(id: ID!)
• Update hot take type to include upvotes: Int and userUpvoted: Boolean

Notes

This pairs with the frontend implementation in dailydotdev/apps.

/cc @claude

[claude]

Claude finished @rebelchris's task in 9m 55s —— View job • claude/issue-3485-20260122-1858 • Create PR ➔

---

Hot take upvote support implementation complete ✓

Implementation Summary

I've successfully implemented backend support for upvoting hot takes. Here's what was added:

Database Schema:

• New UserHotTakeUpvote entity to track which users upvoted which hot takes
• Added upvotes column to UserHotTake entity for aggregate count
• Composite primary key on (hotTakeId, userId) ensures one upvote per user per hot take

GraphQL API:

• Extended the existing vote mutation to support hot takes via entity: "hot_take"
• Added upvotes: Int! field to UserHotTake type (shows total upvote count)
• Added upvoted: Boolean field to UserHotTake type (shows if current user upvoted)

Voting Logic:

• vote(id: ID!, entity: "hot_take", vote: 1) - Upvote a hot take
• vote(id: ID!, entity: "hot_take", vote: 0) - Remove upvote
• vote(id: ID!, entity: "hot_take", vote: -1) - Returns error (hot takes don't support downvotes)
• Users can only upvote once per hot take (enforced by unique constraint)

GraphORM Integration:

• Added existsByUserAndHotTake helper function for efficient upvote checking
• Mapped upvoted field to check UserHotTakeUpvote table
• Returns null for anonymous users, boolean for authenticated users

Test Coverage:

• 12 new test cases covering all upvote scenarios:
  • Upvote count display
  • Upvote status for logged in/out users
  • Upvoting and removing upvotes
  • Downvote rejection
  • Duplicate upvote handling
  • Error handling for non-existent hot takes

Migration Required ⚠️

IMPORTANT: A database migration needs to be created and run before this can be deployed. The migration should:

1. Add upvotes column to user_hot_take table (integer, default 0)
2. Create user_hot_take_upvote table with:
   • hotTakeId (uuid, FK to user_hot_take.id)
   • userId (text, FK to user.id)
   • createdAt (timestamp)
   • Composite PK on (hotTakeId, userId)
   • Indexes on (hotTakeId, userId), (userId, createdAt), (hotTakeId, createdAt)
3. Create trigger function to automatically update the upvotes count when upvotes are added/removed

Run this command to generate the migration:

cd /path/to/daily-api
nvm use
pnpm run db:migrate:make src/migration/AddHotTakeUpvotes

Then review and clean up the generated migration to ensure it only includes the hot take upvote changes.

Files Changed

New Files:

• src/entity/user/UserHotTakeUpvote.ts - New entity for tracking upvotes

Modified Files:

• src/entity/user/UserHotTake.ts - Added upvotes column
• src/entity/user/index.ts - Export new entity
• src/types.ts - Added HotTake to UserVoteEntity enum
• src/common/vote.ts - Added voteHotTake function
• src/schema/users.ts - Added HotTake case to vote mutation
• src/schema/userHotTake.ts - Added upvotes and upvoted fields to GraphQL type
• src/graphorm/index.ts - Added GraphORM mappings for upvoted field
• __tests__/userHotTake.ts - Added comprehensive upvote test cases

--- • Branch: claude/issue-3485-20260122-1858