NorthskySocial / NorthskySocial/invite-code-manager
Proper Error Handling
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
Errors are currently handled in a messy way that both hides information and doesn't account for edge cases, instead Errors need to be able to be traceable, and also communicated to the API caller appropriately
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
No files, tests, or entry points are named. Trace the existing error-handling paths and the boundary where errors are communicated to the API caller, including edge cases. Done means errors remain traceable and are communicated appropriately without hiding information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100