schalkms

In which occasion does this crash happen? May I ask you to provide more details? The stack trace does not even contain **detekt** sources.

> I'm for keeping the current behavior. That's how a lot of other tools/linters work: they rely on the rule name/id for local suppressions. > > This also has the...

This is a good idea for a contributed rule. I really like it! Help is highly appreciated in order to get this rule into detekt. Since there are many more...

Sorry for the late reply. Today I had time to take a look at your repo more thoroughly. I really like your prototype @BraisGabin. The GitHub integration is awesome. This...

To bring this in a production ready state I think detekt has to assert the reported locations in the code by our rules more thoroughly. I once formulated this in...

@BraisGabin do you still actively work on this project? I think it's a hidden gem, which should gain more visibility in the detekt ecosystem. 🙂

Interesting… I remember a few bug reports regarding auto-correct. It’s good that we finally discovered the reason for it. Do you have any ideas how we can fix it in...

That's a good idea. The way to go is to check, which part of the Kotlin compiler reports these cases and then adapt it for this detekt rule via the...

Sorry, I should have described this clearer. Yeah, the idea is to either wrap a Kotlin inspection from the Kotlin compiler or as @cortinico mentioned correctly, reuse the logic from...

@RajatVaryani thanks for your help! That's awesome to hear! We can use every helping hand to further improve detekt and its rules. Sure, I can give you some examples. The...