Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configuration for unknown kapt behavior #45

Open
RBusarow opened this issue Mar 14, 2021 · 0 comments
Open

configuration for unknown kapt behavior #45

RBusarow opened this issue Mar 14, 2021 · 0 comments
Labels
feature New feature or request

Comments

@RBusarow
Copy link
Member

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 RBusarow added the feature New feature or request label Mar 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant