dagger-android dependency in a demo application
- Dominant language
- Kotlin
- Stars
- 1.3k
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm looking at your demo application and trying to figure out the needed dependencies. I've noticed that you are using **Dagger 2** for dependency injection. So I'm just curious why the `com.google.dagger:dagger-android` and `com.google.dagger:dagger-android-processor` are needed? If you are injecting all dependencies manually without help of any android-specific tools from `dagger-android` library.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the demo application's dependency declarations and inspecting the uses of Dagger 2, dagger-android, and dagger-android-processor. Confirm whether each dependency is required; done means the issue has a clear explanation or the unnecessary declarations are identified for removal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100