You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:detekt-tooling is the public api for anyone that wants to implement a detekt client
Current 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 the interfaces, enums and similar classes.
The text was updated successfully, but these errors were encountered:
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?)
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: