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
Refactor :detekt-tooling
#7014
Labels
Comments
Agree, tooling API should be the entry point for all clients - CLI, Gradle plugin and compiler plugin. And it should be used by the IDE plugin if it's not already (but I think it was originally introduced for that purpose?) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
:detekt-tooling
is the public api for anyone that wants to implement adetekt
clientCurrent Behavior
Right now we have a mixture between
:detekt-tooling
and:detekt-cli
. And also:detekt-tooling
has things that shouldn't be part of the API.Context
I think that
:detekt-gradle-plugin
shouldn't use:detekt-cli
. And it should depend on:detekt-core
. But, because we don't want to make:detekt-core
public, we can use:detekt-tooling
as the public api containing only theinterface
s,enum
s and similar classes.The text was updated successfully, but these errors were encountered: