There are cases where I want to debug things like "what is the path from injector to certain injectee" or "what is the set of classes causing an injection cycle" and with fastInit, it's hard/impossible to click through (from Android Studio) to the switching provider impls.
Simple adding dagger.fastInit=disabled to the ksp config doesn't seem to work (i'm guessing maybe the fastinit config in the javacompile task isn't overridden). Would it be possible to drive fastinit through the HiltExtension (default = true)?
There are cases where I want to debug things like "what is the path from injector to certain injectee" or "what is the set of classes causing an injection cycle" and with
fastInit, it's hard/impossible to click through (from Android Studio) to the switching provider impls.Simple adding dagger.fastInit=disabled to the
kspconfig doesn't seem to work (i'm guessing maybe the fastinit config in the javacompile task isn't overridden). Would it be possible to drive fastinit through the HiltExtension (default = true)?