I see from the docs that detekt can validate formatting via ktlint, but can it also format files wit...

# detekt

[Big Chungus]

I see from the docs that detekt can validate formatting via ktlint, but can it also format files with it?

[gammax]

Yes we do have the autoCorrect flag exactly for that

[Big Chungus]

What would gradle cmdline look like for this?

[Javier]

when I was using detekt with the autoformatting, I think just running detekt was autoformatting everything, but not sure, that was long time ago

[Javier]

hope ktfmt being integrated into detekt tho 🙂

[Big Chungus]

Oh? Is there a way to separate out formatting and checking?

[Javier]

not sure tbh, that was long time ago

[gammax]

The gradle cmq line for autocorrect will be --auto-correct but will be available in Detekt 1.19.0 (the next release).

[Big Chungus]

Btw, I've always been curious how custon cli args are implemented in gradle. Could you point me to some code?

[gammax]

Here you go 🙂 https://github.com/detekt/detekt/pull/4202

[Big Chungus]

Wow, can't believe how simple this is

[Javier]

--auto-correct works so because it is a boolean, if it was an string, I think it was --some-task-prop=someString

[Javier]

That was the reason I moved the kamp implementation to Gradle tasks hahah, it was easier to use

[Big Chungus]

Ah, just read in gradle docs today that = is recommended, but optional

[Javier]

--auto-correct if the variable is a boolean set it as true

[Javier]

but if the variable is a string you need to indicate the value, so you need the equals I think

[Javier]

or you mean you can add an space?

[Javier]

--some-task-prop someString // this?

[Javier]

I havent tried it tbh

[Big Chungus]

I meant --my-option="value" is understood as identical to --my-option "value" by gradle

[Javier]

interesting, TIL

[Big Chungus]

But gradle recommends using =. Maybe they have plans to make it mandatory in the future 🤷