KtLint does not magically update behind the scenes. If the version and configuration are unchanged s...

# ktlint

[Paul Dingemans]

KtLint does not magically update behind the scenes. If the version and configuration are unchanged since last successful run than the difference must be in the code.
I am not familiar enough with the plugin to say something about it.

[Piotr Krzemiński]

Can I somehow get debug info on what ktlint does, to go forward with troubleshooting my problem? E. g. to learn what rules are enabled

[Paul Dingemans]

Yeah, use option “-v” (or “--verbose”).

[Paul Woitaschek]

Do you use the cli or some Gradle plugin?

[Piotr Krzemiński]

https://github.com/krzema12/github-actions-kotlin-dsl/blob/97654e0ce10994e64f4a183a7b8ae32e69c075c1/build.gradle.kts#L7

[Piotr Krzemiński]

I didn't have time to test the verbose mode yet

[Piotr Krzemiński]

So, the log showed not all files being processed. Can it be because one Gradle task creates the files, and org.gradle.parallel=true or org.gradle.caching=true makes Ktlint not see all files?

[Piotr Krzemiński]

These two settings were added 3 days ago, approx. when the issue started to happen, so there's high correlation

[Piotr Krzemiński]

@Zongle Wang FYI

[Piotr Krzemiński]

Removing these two options solved my issue, but it's still something worth looking at within probably the Gradle plugin. FYI @jlleitschuh

[Paul Woitaschek]

And are you sure you correctly declared the outputs and task order?

[Piotr Krzemiński]

No :) My knowledge about Gradle is limited

[Paul Woitaschek]

Can it be because one Gradle task creates the files

It sounds like they are generated at build time?

[Piotr Krzemiński]

Yes - adding a task dependency so that ktlint runs after the file generation task should do the job right?

[Paul Woitaschek]

But why would you ktlint generated Code in the first place?

[Piotr Krzemiński]

So that it's more readable when someone browses its source

[Paul Woitaschek]

Ah wow. Okay that's an interesting requirement

[Paul Woitaschek]

Can you post the skeleton of your Gradle task that generates?

[Piotr Krzemiński]

Also, we keep these in version control for now, to exactly see what changes over time. Thanks to formatting, diffs are cleaner. One day we may remove it from VCS

[Piotr Krzemiński]

Yeah, we use the applocation plugin to call some main function: https://github.com/krzema12/github-actions-kotlin-dsl/blob/63ae5c486dd7d2019446c81028d5fd96ad9f8489/wrapper-generator/build.gradle.kts#L32

[Paul Woitaschek]

The correct way would to not use an application plugin but instead a gradle task that declares inputs and outputs.

[Paul Woitaschek]

https://github.com/krzema12/github-actions-kotlin-dsl/blob/5770a1f9ae303351619b226aede55d2276b16648/wrapper-generator/build.gradle.kts#L37

[Paul Woitaschek]

It might work do declare proper task outputs here, i.e.
outputs.dir(project.path….)

[Piotr Krzemiński]

Thanks, I'll tinker around it in spare moment. FYI @jmfayard

[jmfayard]

To be honest, I would rather not reformat the generated code with ktlint and configure ktlint/detekt to ignore it.

[Piotr Krzemiński]

Yes, it's a possible trade-off

[Paul Woitaschek]

I would absolutely do that if I maintained that. ^^

[Piotr Krzemiński]

Ok, I feel convinced: https://github.com/krzema12/github-actions-kotlin-dsl/issues/383

[Piotr Krzemiński]

Thanks for the discussion!