oxidecomputer / oxidecomputer/lpc55_support
Refactor lpc55_sign error handling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
lpc55_sign::Error has become a dumping ground for every function provided in that crate. While there is some overlap between commands, there's also a bunch that is orthogonal. Ideally, lpc55_sign::Error would be broken up into a bunch of different error types so users of the error code don't have to deal with 20 variants that can't possible happen on whatever function they are using.
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 by reviewing lpc55_sign::Error and the functions in the crate that use its variants. Separate errors by the commands or functions that can produce them, then verify that each function's public error type no longer exposes unrelated variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100