mipidisaster / mipidisaster/miLibrary
Device definition files
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Based upon the work done on the BME280 device, it has noticed that it might be worth putting all the specific definitions of devices within a specific file.
As none of these definitions should be used outside of the class source file.
If any of these are needed outside of the class, then it should be a constant within the class, so as to ensure that any changes are correctly impact assessed.
Contributor guide
No contributing guide indexed for this repository
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 with the BME280 device implementation and identify the specific device definitions currently associated with it. Check whether each definition is used outside its class source file; done means these definitions are kept in an appropriate device-specific file, with any externally needed values represented as class constants.
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
- 35/100