Refactor ResourceRegistrar classes (reduce duplicated code)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
We should refactor all the common resource registrar code and move it to the base class. Actual resource-specific classes should just contain a small amount of meta-data (which API model to use, which persistence class to use, etc).
I've already done a pass in the past, but there is still way too much of duplicated code and by refactoring it, we can get rid of substantial amount of duplicated code.
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
The issue does not name specific files, tests, or entry points. Begin by locating the ResourceRegistrar subclasses and their base class, inventory the duplicated behavior, and determine whether the shared code can move safely; done means resource-specific classes contain only metadata and the existing test suite passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100