rubyforgood / rubyforgood/awbw
Give MonthlyReports their own table
Open
Nobody has claimed this yet.
database cleanup
not-ready
post-prod-data-import
stakeholder-question
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 26
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 242
Description
- They're all stored STI-style under Report
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
No files or tests are named. Start by locating the Report and MonthlyReport models and the schema definition, then trace how MonthlyReports are stored through Report's STI setup. Done means MonthlyReports have their own table and the affected persistence behavior remains covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100