kompass
Dagger2
Our great sponsors
kompass | Dagger2 | |
---|---|---|
2 | 50 | |
343 | 17,311 | |
- | 0.3% | |
0.0 | 9.1 | |
over 4 years ago | 7 days ago | |
Kotlin | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kompass
-
Following the architecture
The way Google wants us to handle navigation (in fragment using jetpack navigation) adds too much logic to view. I'm not sure if something changes lately in navigation component, but some time ago it was quite difficult to move navigation to VM layer. Moving navigation from view is difficult, it finally makes things simple when done. I have no advice on how to do that except maybe check this library, though it wasn't updated for some time
-
View Model Doesn’t Have To Depend on ViewModel
kompass seems promising for navigation. Though it's not that difficult to maka a router with SharedFlow of routes (sealed interface or something) and subscribe for it in activity for navigation. I guess something similar could be done in iOS.
Dagger2
- Dagger 2.49 (KSP, @AssistedInject with @HiltViewModel, more)
- Dagger 2.48 adds alpha KSP support
- Dagger KSP update & Breaking changes required to use Dagger KSP
-
Performance and memory impact of the @Singleton annotation in Dagger
There used to be a thing called "releasable references" which was that. It was removed, though: https://github.com/google/dagger/issues/1117
-
Dependency injection with AWS Lambdas in java
As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.
-
Refactoring our Dependency Injection using Anvil
At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.
-
Dagger Python SDK: Develop Your CI/CD Pipelines as Code
Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/
-
Multiplatform dependency injection libraries equivalent to Dagger/Anvil
I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:
-
Dagger 2.43 released with support for multiple instances of the same ViewModel using keys 🎉
Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328
-
Best libraries for Android Developers
Dagger
What are some alternatives?
Slide - Slide is an open-source, ad-free Reddit browser for Android.
Guice - Guice (pronounced 'juice') is a lightweight dependency injection framework for Java 11 and above, brought to you by Google.
PeopleInSpace - Kotlin Multiplatform project with SwiftUI, Jetpack Compose, Compose for Wear, Compose for Desktop, Compose for Web and Kotlin/JS + React clients along with Ktor backend.
Toothpick - A scope tree based Dependency Injection (DI) library for Java / Kotlin / Android.
Weld - Weld, including integrations for Servlet containers and Java SE, examples and documentation
butterknife - Bind Android views and callbacks to fields and methods.
HK2
Dynamic CDI - Dynamic Context Dependency Injection
Apache DeltaSpike - Mirror of Apache Deltaspike
Feather - Lightweight dependency injection for Java and Android (JSR-330)
Tiger
Katana - Lightweight, minimalistic dependency injection library for Kotlin & Android