theupdateframework / theupdateframework/rust-tuf
Change Error enum to be more semantically meaningful
Open
Nobody has claimed this yet.
Feature :: Improvement
Flag :: Help Wanted
Priority :: Low
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
I keep tacking stuff on to it, but realistically it should have just an Opaque error type to catch all the IO / HTTP / whatever stuff, and then other values for TUF failures.
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 locating the Error enum and listing its existing variants. Review how IO, HTTP, and TUF failures are represented, then define a semantically meaningful grouping that preserves the proposed Opaque category and clearly identifies TUF failures. Done means the enum design and its impact on callers are agreed and consistently applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100