Purple Forest: New Feature: Rebloom
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- full-stack
Research direction
Start by locating the existing bloom and feed entry points, then clarify whether a rebloom uses the original timestamp, the rebloom timestamp, or both. Define the UI distinction between original blooms and reblooms, attribution for both users, follower visibility, and the rebloom count before implementation; done means these behaviors are specified and covered.
Written by the indexing model from the issue text.
Description
When a user sees a bloom they want to share, they want to be able to press a button to "re-bloom" the bloom.
This should add a bloom to their feed and should be shown to their followers (as if they'd bloomed it themselves), but but should make clear in the UI both who originally bloomed it, and who re-bloomed it. It should be obvious in the UI that this is different from a bloom they bloomed themself.
A bloom should also show how many times it has been re-bloomed (but maybe not show anything special if it's never been re-bloomed).
I'm not sure what timestamp a rebloom should have/show. Maybe the original bloom time? Maybe the time of the rebloom? Maybe both? Unclear...
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Legacy-Code
-
🏝️ Priority Stretch 📅 Sprint 1 Module-Legacy-Code Optional Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Legacy-Code Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 30/100
-
🏕 Priority Mandatory 📅 Sprint 2 Core Module-Legacy-Code Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
:gear: bug 🏕 Priority Mandatory 📅 Sprint 2 Core Module-Legacy-Code Submit:PR
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
:gear: bug 🏕 Priority Mandatory 📅 Sprint 1 Core Module-Legacy-Code Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in CodeYourFuture/Module-Legacy-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·