it is not on the classpath).ĭagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. This release fixes a recently noticed, but long-standing bug ( #3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e.
Make it so that map keys used with in Kotlin code do not need to use the notation. The default ViewModelProvider.Factory from activities and fragments can be used directly with the backstack entry as the owner. hiltNavGraphViewModels is now no longer necessary to use with navigation backstack entries as the owner. Fixes #2328 and #3232 where getting multiple instances of with different keys would cause a crash. Fix #3464 where SPI plugins were not being invoked with Hilt's Gradle Plugin aggregation ( enableAggregatingTask) turned on. To build with SDK 31, AGP users will need to use AGP 7.0+. These libraries require building with SDK 31. androidx.navigation users will need to update to 2.5.0 to interoperate. As part ViewModel bug fixes, dependencies were updated as below. This is unlikely to happen though unless overridden by the user to return null. Hilt now throws if the base activity/fragment class’s getDefaultViewModelProviderFactory() returns null. 
What’s New In Hilt Potentially Breaking Changes
Fixes #3401 where Dagger generated mismatched parameter names in subcomponent factory method implementations when the original factory method is in a separate build unit from the component that implements it. 
However, this requirement has been recently reverted in XProcessingĪnd Dagger 2.43.2 should support java 8 again (see issue #3495).
Note: Dagger 2.43/2.43.1 require java 11 due to a change in Dagger's XProcessing dependency. What’s New In Dagger Potentially Breaking Changes
0 kommentar(er)
