Today is Kotlin 2.3 day, and ~60% of my projects c...
# detekt
e
Today is Kotlin 2.3 day, and ~60% of my projects can't update because of Detekt. A big reason the v2 alphas are a no go for me is because there's external tooling around Detekt that doesn't want to update to use them because it looks like there are still breaking changes that need to happen before v2 is stable. Is it possible to prioritize completing the breaking changes for v2 so that external tooling can be updated?
☝️ 4
g
Yes we can prioritise that but we don't have an ETA for 2.0.0 stable
e
Understood and appreciated. Minimizing breaking changes would go a long way.
➕ 1
s
And I guess the need to upgrade Detekt to 2.x emerged from the false-positives you get with Kotlin 2.3. and Detekt 1.x with type resolution?
e
I have to double check, but I'm pretty sure they're all false positives, and no outright breakage, but there's a lot of repos I need to look over.
r
Without me having tried the upgrade yet, what's breaking in version 1 with the new Kotlin version? I'd hope that upgrading Kotlin is independent of the Detekt migration.
s
See my message from before, you simply get a ton of false-positives.
☝️ 1
r
Only with type resolution?
s
Yes.
d
for us, it's context parameters, and we got crashes on detekt 1.x
➕ 1
we had to update to 2.x alphas for context params to work
👌 1
j
I didn't care about any false positive, I just updated to alphas because I was getting build crashes, do not remember which ones tho