android / android/nowinandroid
[FR]: Adding error management example with best practices
- Dominant language
- Kotlin
- Stars
- 21.8k
- Forks
- 4.6k
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 2
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the problem
Now in android app is a well structured app and an interesting starting point to study how create an android app with a good architecture.
However, reviewing the code, i've noticed the absence of a good "error handling" example, in particular where the error pass via all the app layers and through the various mapping and anti-corruption layers.
I can work on this topic and try to submit a pull request if for you sound acceptable.
### Describe the solution
Add error management at least in one feature / use case
### Additional context
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Review the Android app's existing feature and use-case structure, focusing on how errors move through its layers, mappings, and anti-corruption layers. Done means one feature or use case contains a documented error-management example that demonstrates this flow; no specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100