![]() ![]() ![]() This may break apps that are providing the same binding with different wildcards, e.g. Breaking changes The dagger.ignoreProvisionKeyWildcards is now enabled by default We don’t expect these changes to affect most users. These changes were made to better support Dagger usage with Kotlin sources, and make the migration from KAPT to KSP more seamless. There are also a few potentially breaking changes included with this release. The current list of known issues can be found here. Please apply due diligence when enabling ksp and report any bugs or performance issues at. So far we’ve focused mainly on trying to ensure correctness rather than optimize performance. If you depend on androidx.hilt:hilt-common or androidx.hilt:hilt-work they will need to be updated to at least 1.1.0-alpha01.Īlso note that Dagger’s KSP processors are still in the alpha stage. Ensure that there are no kapt processors that generate classes that need to interact with Dagger (see ).Migrate any Dagger SPI plugins to the new Dagger SPI plugins API (with KSP support) (see ).Follow the basic setup to migrate Dagger’s processors from kapt to ksp (see ).In order to use Dagger’s KSP processor you will need to: Instructions for using the Dagger/Hilt KSP processors can be found at. Dagger 2.48 includes the alpha release of the Dagger and Hilt KSP processors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |