Open ZacSweers opened 4 years ago
Thanks, noted. Will target a fix for 0.3.1.
I took at shot at this in #53 but it is not fully fixed yet.
New behaviors
kapt
arguments during plugin application. This means I have to pass arguments very early but at that time dependencies might not be available. Technically I can do configuration.dependencies.all {}
or whenObjectAdded
but that cause eager evaluation and I want to avoid it for now. Created https://youtrack.jetbrains.com/issue/KT-39521The following options were not recognized by any processor
warning was spit out based on supported options alone but it seems to check for supportedTypes as well. Checking for dagger presence alone might not be sufficient to avoid this error. Failing functional test.I will keep this open and look for any workaround.
Update: I saw this https://github.com/JetBrains/kotlin/commit/19708cfa8708bc36da17601f13fe9921d7a380ef and also now Kapt options are using provider
instead of evaluating eagerly. I will investigate if this can be fixed soon,
@arunkumar9t2 i also have this issue an nothing is being generated in kapt3/classes/ folder.
This leads to warnings in kapt when it doesn't run