ModuleCheck icon indicating copy to clipboard operation
ModuleCheck copied to clipboard

configuration for unknown kapt behavior

Open RBusarow opened this issue 4 years ago • 0 comments

Additional kapt matchers can be defined using additionalKaptMatchers in the extension, but what about processors which aren't defined? If a processor is present in the project but not defined in ModuleCheck, it will currently default to "unused" and fail the task.

Valid options seem to be:

  • Strict mode
    • fail the task with a reason such as "undefined kapt processor"
    • this would require the developer to add the processor to additionalKaptMatchers in order to continue.
  • Warning mode
    • log a warning that there's an undefined processor and suggest adding it
  • Silent mode
    • Don't do anything.
    • This seems somewhat valid if the developer only cares about the big named processors, perhaps maybe only Dagger. Silent mode is a quick and dirty way of getting what they need without the hassle of adding anything else.

RBusarow avatar Mar 14 '21 21:03 RBusarow