[Android] Could you share the actual bugs that Dagger's Dependent Component solved?
Open
Nobody has claimed this yet.
Android
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
As opposed to SubComponent which is easier to implement
For example, did Transport team accidentally used some services meant for Food delivery only?
Or did logged out components wrongly used some logged-in-only services?
Or was it all hypothetical and Dependent Component simply enforced code to be cleaner?
Contributor guide
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 reviewing the Android architecture material that explains Dependent Components and SubComponents, then trace how the Transport, Food delivery, logged-out, and logged-in examples relate to those boundaries. Done means documenting whether these components solved observed bugs or primarily enforced cleaner separation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100