Link New Status Data Models to Existing Functionality
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Once we have the data models defined and implemented, we'll need to link them to the existing functionality where status files are updated. This happens mainly in the `step.py` file and the `tasks.py` file. I want to do this prior to even touching the status command implementation itself so the PR for that isn't giant (it probably still will be).
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 reading the status-file update paths in `step.py` and `tasks.py`, then identify how the new status data models are defined and implemented. Link those models into the existing update functionality before working on the status command; done means those updates use the new models without implementing the command itself.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100