rubyforgood / rubyforgood/Flaredown
[BUG] newly added symptoms not saving for availability in future checkins
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 21
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 16
Description
Another related bug reported:
I just downloaded Flaredown, and as I was adding in my symptoms for the day, I noticed that there was no way to add the previously entered symptoms and was wondering if that could be something that gets added in the future?
I think it's something in https://github.com/rubyforgood/Flaredown/blob/c28d36bd69a98888a2cfbeef626af0f505285457/backend/app/services/checkin/creator.rb#L12
newly added symptoms not saving for availability in future checkins
Contributor guide
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.
Research direction
Start in backend/app/services/checkin/creator.rb at the linked line and trace how symptoms are handled when a check-in is created for a future date. Reproduce the reported flow, then verify that newly added symptoms remain available and are saved for future check-ins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100