-[x] I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title

• My changes meet the requirements of the task
• I have tested my changes
• My changes follow the style guide

Briefly explain your PR.

✨ Re-bloom Feature Implementation

This PR implements the Re-bloom feature in the Purple Forest application, allowing users to reshare blooms while keeping a clear distinction between original blooms and reblooms. The feature covers backend data modeling, API endpoints, state management, and frontend UI changes, aligning with the architecture of the application.

1. Feature Overview

Users can re-bloom an existing bloom by pressing a new Re-bloom button.

A rebloom adds the bloom to the user’s feed and their followers’ feeds as if they posted it themselves, but it clearly shows:

Original author of the bloom

User who rebloomed it

Each bloom displays rebloom count and last rebloomed timestamp when applicable.

Profile pages continue to display only original blooms; reblooms are shown only in the Home Feed.

2. Database Changes

A new table reblooms was created to track reblooms:

Column Type Notes
id bigint Primary key
original_bloom_id bigint Foreign key to blooms, not null
rebloomed_by integer User ID who performed the rebloom, not null
rebloomed_at timestamp without timezone Timestamp of rebloom, default CURRENT_TIMESTAMP

Unique constraint ensures a user cannot rebloom the same bloom twice.

3. Backend / API Changes

Endpoints added:

POST /rebloom/<bloom_id> → creates a rebloom if it doesn’t exist for the user

GET /reblooms/user/ → fetches reblooms made by a specific user

Bloom data model updates:

Added optional fields: rebloomer, rebloom_count, last_rebloomed_at

New backend functions:

has_user_rebloomed(original_bloom_id, user_id) → checks if user already rebloomed

add_rebloom(original_bloom_id, user_id) → inserts a rebloom record

get_reblooms_for_user(username) → fetches all reblooms by a user as Bloom objects

Feed query updates:

get_blooms_for_user now includes rebloom count and last rebloom timestamp

Reblooms are merged into the feed and ordered by their rebloom timestamp for proper timeline display

4. Frontend Changes

Timeline component (timeline.mjs):

createBloomWithRebloom() renders rebloom info if available: rebloomer, count, and timestamp

Adds a Re-bloom button to each bloom that supports reblooming via event delegation

Home view (home.mjs):

Listens for rebloom button clicks

Calls API to perform rebloom and refreshes timeline and profile state

API service updates:

rebloom(bloomId) function handles rebloom requests and updates state accordingly

5. State Management

State is updated via central state object, following the existing SSOT and unidirectional data flow.

Reblooms trigger state-change events to automatically re-render the Home Feed.

6. Summary of Changes

New database table to track reblooms

API endpoints for creating and fetching reblooms

Bloom model updates to include rebloom metadata

Feed and timeline rendering now supports rebloom information

Frontend event handling for rebloom actions

Profile pages unchanged – reblooms excluded

This implementation ensures a clear distinction between original blooms and reblooms, preserves original content, tracks rebloom counts, and integrates seamlessly with the existing Purple Forest SPA architecture.