Refactor Status Classes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
The status classes will need to be refactored to no longer read from files (well, maybe we keep this in the first release for backwards compatibility unless we decide to put this in Merlin 2.0) and instead read from the Merlin database. May want to consider splitting the Status and DetailedStatus classes into more specialized classes, but may not be necessary if database makes the logic in these classes a lot easier to maintain.
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 by locating the Status and DetailedStatus classes and tracing where they currently read status files. Review Merlin's database status models and the first-release versus Merlin 2.0 compatibility requirement, then define the class boundaries and migration scope before changing code; done means status data is read from the database without breaking the intended compatibility behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100