OpenDevicePartnership / OpenDevicePartnership/ec-slimloader
Untangle MCXA IFR
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 14
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 1
Description
The IFR is not properly modeled in the codebase and is intertwined with the business logic. This should be separated.
I had already built the model in my branch here: https://github.com/diondokter/ec-slimloader/blob/baa3f1bdf4e03f7c1d6f3af23c0e93075a1ffef8/libs/mcxa-ifr/src/lib.rs
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 existing MCXA IFR handling and compare it with the proposed model in libs/mcxa-ifr/src/lib.rs at the linked branch. Trace where the IFR is intertwined with business logic, then separate those responsibilities while preserving current behavior. Done means the IFR is modeled independently and the affected behavior remains covered by the repository's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100