| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 399f4f61132f363e9479e59c550a7bcf005922d8.
Reason for revert: b/187908823
Change-Id: I81f7cd3672e65ce1f7e1fa846b6c3e2f87147a26
|
|
Fixes #2577
RELNOTES=Fixes #2577: Add flag to disable cross-compilation root validation.
PiperOrigin-RevId: 370573954
|
|
compilation unit that do not have test-specific bindings, rather than generating new components per-test. This can significantly reduce the amount of generated code for large projects with many test classes that do not provide test-specific bindings.
This is currently off-by-default behind a compiler flag. This may be turned on by default in a future release.
RELNOTES=Only generate and compile a single _HiltComponents class for test roots in the same compilation unit that do not have test-specific bindings, if flag enabled.
PiperOrigin-RevId: 366281911
|
|
When Hilt Android is run on a module that contains no entry points, KAPT will log an error about `disableAndroidSuperclassValidation` not being a support option. This is because the Hilt Gradle plugin will add this option when applied but if no entry points exists, no processor actually accepts that option.
With this fix, all Hilt processors accept these options (though they are unused). This will prevent KAPT from logging these warnings in most cases.
It is still possible for warnings to be logged, for example if the Hilt plugin is applied, but Hilt isn't used but for those cases the user can simply skip applying the plugin.
Fixes #2040
Closes #2372
RELNOTES="Reduce the possibility of KAPT logging warnings due to no processor supporting `disableAndroidSuperclassValidation` when no Android entry points are in the source module."
PiperOrigin-RevId: 360836064
|
