Proper error handling
Open
bug
enhancement
- Dominant language
- Haskell
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Error handling with `error` is not the best plan. This library should use some more reasonable error handling strategy.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating uses of `error` throughout the library and determine the current error-handling behavior. This issue is done only when a specific replacement strategy is agreed and consistently applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- audio-video-rtc
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100