A reflection-based implementation of the Dagger dependency injection library for fast IDE builds and tests.
More info soon...
Current release: 0.1.0
Snapshots of the next development version are available in Sonatype's snapshots
repository.
There are two methods of integrating Dagger Reflect to replace Dagger:
This approach still uses an annotation processor to generate implementations of your component interfaces which then call into the reflection runtime. The annotation processor is fully incremental and does no validation to ensure minimal overhead.
-
Pros:
- Your code does not have to change when switching between Dagger and Dagger Reflect (modulo limitations below)
-
Cons:
- The use of an annotation processor still causes a build-time impact
For an Android build, configure your dependencies:
dependencies {
if (properties.containsKey('android.injected.invoked.from.ide')) {
debugAnnotationProcessor 'com.jakewharton.dagger:dagger-reflect-compiler:0.1.0'
debugApi 'com.jakewharton.dagger:dagger-reflect:0.1.0' // or debugImplementation
} else {
debugAnnotationProcessor "com.google.dagger:dagger-compiler:$daggerVersion"
}
releaseAnnotationProcessor "com.google.dagger:dagger-compiler:$daggerVersion"
api "com.google.dagger:dagger:$daggerVersion" // or implementation
}
This will enable Dagger Reflect only for debug builds in the IDE.
This approach avoids all annotation processor usage enabling the quickest builds at the expense of having to change your production Dagger code. In order to avoid the need to
-
Pros:
- No annotation processors!
-
Cons:
- Rewrite bridges into generated code to call into runtime library.
- Special care has to be taken for R8/ProGuard (for now).
dependencies {
if (properties.containsKey('android.injected.invoked.from.ide')) {
debugApi 'com.jakewharton.dagger:dagger-reflect:0.1.0' // or debugImplementation
} else {
debugAnnotationProcessor "com.google.dagger:dagger-compiler:$daggerVersion"
debugApi 'com.jakewharton.dagger:dagger-codegen:0.1.0' // or debugImplementation
}
releaseAnnotationProcessor "com.google.dagger:dagger-compiler:$daggerVersion"
releaseApi 'com.jakewharton.dagger:dagger-codegen:0.1.0' // or releaseImplementation
api "com.google.dagger:dagger:$daggerVersion" // or implementation
}
This will enable Dagger Reflect only for debug builds in the IDE.
When creating a component, builder, or factory in your code, replace calls into generated code with
calls into the static Dagger
factory with the associated class literal.
-MyComponent component = DaggerMyComponent.create();
+MyComponent component = Dagger.create(MyComponent.class);
-MyComponent.Factory factory = DaggerMyComponent.factory();
+MyComponent.Factory factory = Dagger.factory(MyComponent.Factory.class);
-MyComponent.Builder builder = DaggerMyComponent.builder();
+MyComponent.Builder builder = Dagger.builder(MyComponent.Builder.class);
Because Dagger Reflect is implemented using a Proxy
, only interface components,
factories, and builders are supported.
In order for a factory or builder which is backed by a Proxy
to create an instance of the
enclosing component which is also backed by a Proxy
, the component has to be public.
Pretty sure no one but Google uses this. PRs welcome.
Copyright 2018 Jake Wharton
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.