Which is the Detekt public api? #4117
BraisGabin
started this conversation in
General
Replies: 1 comment
-
Currently, we have I agree with you that we don't necessarily keep binary compatibility - It should be a judgment call to determine changes to those modules. On the other hand, we often draw a conclusion which maintains binary compatibility. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm wondering which modules should be consider public api and which are internals. And then, for those that are public, what type of compatibility should we provide:
For example, I think that detekt-test and detekt-test-utils should be consider public. For example I use both in some custom rules: https://github.com/BraisGabin/detekt-junit-rules/blob/main/build.gradle.kts
But I think that we don't need to keep binary compatibility in those.
I think that this is important because we should simplify our public api for 2.0 because now it's a mess: For example, the cli module right now is kind of a public api but it shouldn't.
Beta Was this translation helpful? Give feedback.
All reactions