Overview

ℹ️ This is ticket 1/6 of #1038 Epic: Extract Partner Config from Frontend to Database.

We need to store partner branding and social link configuration in the database instead of hardcoding it in the frontend. This ticket creates a database migration to add the necessary columns to the partner table. All new fields should be nullable — we will populate them in a later step and do a follow-up migration to enforce non-null constraints where appropriate.

❗️ Blockers:
None

Action Items

• Generate a new TypeORM migration file (follow existing naming convention: {timestamp}-bloom-backend.ts
• Add the following nullable columns to the partner table:

• Add the corresponding @Column decorators to PartnerEntity (src/entities/partner.entity.ts) with { nullable: true }
• Ensure the migration has both up (add columns) and down (drop columns) methods
• Run the migration locally and verify the columns are created
• Run existing tests to ensure nothing breaks: npm run test

Resources

• Existing migration example: src/migrations/1748540025892-bloom-backend.ts
• Entity to update: src/entities/partner.entity.ts
• TypeORM column docs: https://typeorm.io/entities#column-options