When an annotation is placed on a property in Kotlin, it’s not clear whether Java will see that annotation on the field of the property or the method for that property. Include these compiler arguments in your adle file to make Dagger more performant at build time: If you’re using a lower version, disable code formatting to improve your build time (see code below). This option was added in Dagger v2.18 and it’s the default behavior (doesn’t generate formatted code) in v2.23. In case you’re using a lower version, you need to add a few lines of code (as shown below) if you want to benefit from it.Īlso, you can tell Dagger not to format the generated code. To improve your build time, Dagger added support for gradle’s incremental annotation processing in v2.18! This is enabled by default in Dagger v2.24. Thanks to all of the contributors that commented there! kapt build improvements This post was inspired by some of the suggestions in this Dagger issue that goes through best practices and pain points of Dagger in Kotlin. This post will highlight areas where they differ and how you can use Dagger with Kotlin without having a headache. This article focuses on using Dagger with Kotlin, including best practices to optimize your build time and gotchas you might encounter.ĭagger is implemented using Java’s annotations model and annotations in Kotlin are not always directly parallel with how equivalent Java code would be written. This month, a new tutorial was released to help you better understand how it works. It provides fully static and compile-time dependencies addressing many of the development and performance issues that have reflection-based solutions. Dagger is a popular Dependency Injection framework commonly used in Android.

Dagger kotlin