Releases: adennie/fb-android-dagger
1.0.7
1.0.6
This release includes two new injecting base classes:
- InjectingAppWidgetProvider
- InjectingActionBarActivity
In addition, InjectingApplication was enhanced with new addSeedModules() method to facilitate unit testing with test-method-specific dagger modules. See http://andydennie.com/2014/12/16/initialize-your-android-components-dagger-object-graph-on-a-per-method-basis-in-your-robolectric-tests/ for a detailed explanation of how to use this feature.
Finally, InjectingServiceModule's provideApplicationContext() provider method was replaced with provideServiceContext, which seems to make more sense in that, uh... context.
1.0.5
New in this release:
- update dagger dependency to version 1.2.1
- copy needed bits from Guava and remove the Guava dependency, reducing the library size considerably (contributed by Tobias Preuss)
- modify Android and support v4 dependencies to use the group IDs, artifact IDs, and version IDs created by the Maven Android SDK Deployer.
1.0.3
1.0.2
This release tweaks the handling of configuration changes (e.g. orientation changes).
Previously, InjectingActivity's onCreate method didn't set up its graph or inject itself until after calling super.onCreate. Since that call to super.onCreate would trigger a call to a retained InjectingFragment's onAttach method, when that InjectingFragment tried to extend the activity graph, it would generate an NPE due to the activity graph not being initialized yet.
In this release, InjectingActivity initializes its graph an injects itself before calling super.onCreate.