Hello team, is it expected that even after autocorrecting something the task still fails? If after c...

# detekt

[sanogueralorenzo]

Hello team, is it expected that even after autocorrecting something the task still fails? If after correcting the only issue (which has autoCorrect true) wouldn't it make sense to not have a build failure?

[schalkms]

Does the following issue describe the problem that you experience?

[schalkms]

https://github.com/arturbosch/detekt/issues/1836

[sanogueralorenzo]

Hello @schalkms yeah exactly, last activity looks it is from Sep 6 🤔

[sanogueralorenzo]

Looks like it is still being discussed, right? I can't see a good reason to report it but if there is, having something like the suggested excludeCorrectable in the .yaml file would be another solution too! (For the above case). The main usecase that I saw in my current company is that people run the ./gradlew detektAll task before pushing and they seem to be confused because it always fails even if all the issues were autoCorrectable (and were fixed during the top level detektAll task run).

[sanogueralorenzo]

oh looks like you pushed a commit on Aug 22 and there were already a few releases since then. Do you want to make a sample project so you can reproduce it? Or am I missing some flag? 🤔

[schalkms]

I haven't got the time to push this fix further.
Some tests as well as the exclusion in the BuildFailure report are missing. I hope that I have time to get back at this task soon.

[schalkms]

Thanks for the feedback btw 🙂