From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

spotless allows passing any file, even in different projects, so you can just apply spotless on buildSrc and add the build file itself

<@U05F2SX4DG8> you are looking for <https://github.com/pinterest/ktlint> the one also does formatting for `build.gradle.kts` files.

<@U01DUV4Q882> That's interesting, are you referring to passing any file while configuring spotless, or on the command line when running `spotlessCheck` or `spotlessApply`?
If the latter, I'm not sure how to go about doing that, since I don't think they accept any flags or configuration, like `./gradlew spotlessCheck path/to/file` would try to run the last one as a task

<@UTF3J30MB> oohh, yes I've seen that, I just haven't seen a way to tell gradle to sort of...run that on itself. Since the gradle files aren't part of the "real" Java codebase, from my understanding gradle is "blind" to them, they're not caught under any convention

In other words if spotless is configured as part of the Java convention, I don't know as part of *what* convention (or otherwise!) to add ktlint

I am using ktlint directly in the project. Applying plugin to the module will add a task `:module:ktlintKotlinScriptFormat` The one will do the formatting of the `.gradle.kts` script file for you.

I don’t know about the combination of ktlint + spotless, I prefer ktfmt over ktlint which is supported by spotless too

<@U01DUV4Q882> That was actually surprisingly simpler than I expected
```spotless {
  kotlin {
    ktfmt()
    target("**/*.gradle.kts")
  }
}```
That also catches the bazillion subprojects, so no need to scratch my head on how to apply that plugin for all the subprojects, which is good

Thanks! It really was a case of just doing it

yeah, indeed you can apply it in the root project only and pick all kt and kts files in all folders, so all files are processed, but it would be better to do it per project in order to parallelize the tasks execution 

and remember to exclude build directories to avoid formatting unnecessary code 

You're very correct, I was very confused before throwing in a:
```    targetExclude("**/build/")```

ktlint-gradle will automatically include your build scripts in the linting. they lint under a different task as well to provide some separation between your source and buildscripts