London | 25-SDC-July | Fatma Arslantas | Sprint 1 | New Feature: Rebloom

[AFatmaa]

Learners, PR Template

Self checklist

• 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

Changelist

I implemented the "Re-bloom" feature, allowing users to share blooms from other users.

• I added a rebloom_id column to the blooms table to link copies to the original bloom.
• Updated blooms.py to fetch the original sender and calculate the re-bloom count using SQL joins and COALESCE.
• Added a new do_rebloom endpoint to handle the requests.
• Registered the new route /bloom/<id>/rebloom in main.py.
• Updated index.html to include a "Re-bloom" button and a "Re-bloomed by" info section.
• Updated bloom.mjs to handle the button click and display the original sender's name if the post is a re-bloom.
• Added the rebloom function to api.mjs.

Questions

I don’t have any questions, thank you!

[illicitonion]

This generally looks great, and particularly the SQL design to use joins to relate the data back to the original bloom makes a lot of sense!

UI-wise, a couple of things to consider:

1. What order should reblooms be shown in the timeline? The original bloom time? The rebloom time? Both?
2. It may be nice to expose "who rebloomed this" on the originals somehow

But these are super optional - the implementation and UX both look great here, well done!