I have a question related to detekt output in gradle build scans. Is there a way to make the failure...

# detekt

[Ward Bonnefond]

I have a question related to detekt output in gradle build scans. Is there a way to make the failure reasons show up in the main summary on the build scan? This must be a misconfiguration in the detekt task itself because android lint is able to show the failure reasons in the task failure message. When it's one module it's not a huge deal, but if multiple modules have failures it's a pain to have to dig into the console log for each

[Brais Gabin]

How does Android lint looks like?

[Ward Bonnefond]

Android lint basically restates all the problems in the final task output

[Ward Bonnefond]

Screenshot 2024-02-29 at 3.30.10 PM.png,Screenshot 2024-02-29 at 3.30.26 PM.png

[Brais Gabin]

Well, it shows the first one. But I think that have sense because I assume that, usually, you just add one issue per module (once you have detekt completely integrated). Open an issue showing the differences and exposing a bit why the lint message is more useful and I think that can be done

[Ward Bonnefond]

Awesome, I'll write something up! And yeah even if there were multiple lint issues for a single module, it would show them all here without needing to drill down into the console output for that particular task

[Brais Gabin]

it would show them all here without needing to drill down into the console output for that particular task

That's not what android lint does. It just show one issue.

[Ward Bonnefond]

Oh you're right. It does only show the first error