What’s new in Dagger

Potentially breaking changes

As of this release, Dagger’s generated class will no longer extend the user-defined @Component annotated class (885b16d). This change was done to improve build times in certain scenarios by avoiding a known javac bottleneck. However, it may also be a breaking change for some users. For example

// This will fail as of Dagger version 2.42
DaggerMyComponent component = DaggerMyComponent.create();

// Do this instead:
MyComponent component = DaggerMyComponent.create();

For migration purposes, we’ve added a temporary javac flag that can be used to re-enable the legacy behavior (the flag is disabled by default).

-Adagger.generatedClassExtendsComponent=ENABLED

This flag will be removed in a future version of Dagger.

What’s new in Hilt

Bug fixes

• Fix two issues (e3d4468):
  1. matchingFallbacks being ignored work with Hilt.
  2. Hilt causing jetifier to execute twice.
• Allow Hilt view constructor to contain non-declared types. (dc76e82)
• Fix #3222. Generated fragment code previously would cause a Lint issue around LayoutInflater.from(). (850fc84)
• Fix #3329 where modules in a package with non-standard capitalization could cause an error in the Hilt Gradle Plugin. (029fe57 and 329915f)