rubyforgood / rubyforgood/human-essentials

Review for unused fields --> clean up

Open
#3,805 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core team stale
Dominant language
Ruby
Stars
593
Forks
593
Avg merge
4d 22h
Merged PRs (30d)
41

Description

Summary

With the partner merge and the user roles there are some fields that are no longer used. We should clean these up.

Why

Tech debt. Mitigating future developer confusion

Details

1/ Review to check what fields aren't used anymore
2/ Clean up those fields
3/ Also clean up these fields on the partner profile (they were removed from the user intefaace a year ago)

evidence-based description
verified successes of program
turn away child care
incorporate plan
responsible staff position
trusted pickup
serve income circumstances
internal db
MAAC program
pickup method
ages served

Criteria for completion

  • Fields that are no longer used due to partner merge/rollify adoption, and last year's profile simplification (and no others!) are removed from the database.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the user and partner profile fields listed in the issue and tracing which are still used after the partner merge, rollify adoption, and profile simplification. Verify that only the confirmed unused fields are removed from the database, with no other fields affected; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
backend, database
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.