Sourced from com.google.dagger:hilt-android's releases.
Dagger 2.48.1
Bug Fixes
Fixes #4063, #4054: [KSP]: Fixes some incremental processing issues with KSP (c8a568956) Fixes #4046: [KSP] Fixes "Unexpected element" in XProcessing library (https://github.com/androidx/androidx/commit/bdc1bb06d4f5dbd574bb66cef674ba31846eb4d3) Fixes #4059: [KSP] Align behavior of generic inline types in KSP with KAPT in XProcessing library (https://github.com/androidx/androidx/commit/b0fa9cf493458a1f3b35a1d68298552e3eaae678) Fixes #3980: Fixes Lint crash with AGP 8.1.0. (e651294c2) Fixes #4055: Fixes issue with using generic types in Dagger's ClassKey (9852b4237)
Dagger 2.48
Dagger/Hilt KSP support
Dagger 2.48 includes the alpha release of the Dagger and Hilt KSP processors.
Instructions for using the Dagger/Hilt KSP processors can be found at https://dagger.dev/dev-guide/ksp.
In order to use Dagger’s KSP processor you will need to:
- Follow the basic setup to migrate Dagger’s processors from
kapttoksp(see https://dagger.dev/dev-guide/ksp#setup).- Migrate any Dagger SPI plugins to the new Dagger SPI plugins API (with KSP support) (see https://dagger.dev/dev-guide/ksp#new-dagger-spi-plugin-with-ksp-support).
- Ensure that there are no
kaptprocessors that generate classes that need to interact with Dagger (see https://dagger.dev/dev-guide/ksp#interaction-with-javackapt-processors).If you depend on
androidx.hilt:hilt-commonorandroidx.hilt:hilt-workthey will need to be updated to at least 1.1.0-alpha01.Also note that Dagger’s KSP processors are still in the alpha stage. So far we’ve focused mainly on trying to ensure correctness rather than optimize performance. Please apply due diligence when enabling
kspand report any bugs or performance issues at https://github.com/google/dagger/issues. The current list of known issues can be found here.There are also a few potentially breaking changes included with this release. These changes were made to better support Dagger usage with Kotlin sources, and make the migration from KAPT to KSP more seamless. We don’t expect these changes to affect most users. Please see below for more details.
Breaking changes
The
dagger.ignoreProvisionKeyWildcardsis now enabled by defaultThis may break apps that are providing the same binding with different wildcards, e.g.
Foo<Bar>andFoo<? extends Bar>.Fix: See https://dagger.dev/dev-guide/compiler-options#ignore-provision-key-wildcards for suggestions on how to fix this. If fixing is not an immediate option, you can still disable the flag with
dagger.ignoreProvisionKeyWildcards=DISABLED.
@Bindsassignability checkUnlike KAPT, KSP takes nullability into account when checking if a type is assignable to another type. This changes the behavior of Dagger’s
@Bindsusage validation such that a type that was assignable in KAPT may no longer be assignable in KSP. For example:// Incorrect: this compiles successfully in KAPT but the compilation fails in KSP @Binds fun bind(impl: FooImpl<Bar?>): Foo<Bar>Fix: To fix this breakage, users should update the parameter or return type in the method such that they are actually assignable when taking nullability into account. For example:
// Correct: this compiles successfully in KAPT and KSP </tr></table>
... (truncated)
2d9ba60
2.48.1 release378535e
Refactor ResolvedBindings and LegacyBindingGraph to include the
ComponentPath.fd907cb
Allow sharding for Dagger compiler tests.558cc51
Fix Dagger's incremental processing for KSP.5cc209c
[Refactor]: This CL refactors a few things in
ComponentDescriptor.e8f5f2b
Drop latest XProcessing jars into Dagger.7412301
Internal changes76bde06
Rollback of "[Refactor] Remove duplicated logic in
BindingGraphFactory"e651294
Fix Lint crash with AGP 8.1.0. See google/dagger#4023...47953aa
[Refactor] Remove duplicated logic in
BindingGraphFactory.