Handle API errors
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 52
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
The code for handling errors is actually present. But the errors from the API are not being propagated to the next level. (They throw an exception rather than return an error as the higher level expects).
For example, `api.createRoom()` should return a null when there is an error, so that caller can process the error properly.
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 at the api.createRoom() entry point and trace how API exceptions are handled and passed to higher-level callers. The work is done when API errors return null instead of throwing, allowing the caller to process the error as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100