InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Moving class constructors to SystemTask
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Currently everything is constructed in main and passed to both DisplayApp and SystemTask. We could move almost everything, including DisplayApp to SystemTask, to limit their scope. I want your feedback on this before I create a PR, so I won't have to maintain the PR for long.
This relates to #1468, as it shows how the scope of MotorController can be limited for example.
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 tracing how constructors are assembled in main and passed to DisplayApp and SystemTask. Read issue #1468 for the related MotorController scope example; the work is complete only once the proposed ownership boundaries are agreed and the affected construction flow is consistently updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100