Jeremy Mailen

Good point, although when format did something the workspace is dirty and some CI flow might need to detect that with a distinct exit result. We have `ignoreFailures` to handle...

Yeah, as @mateuszkwiecinski points out ktlint has some built in conventions, which align with the editorconfig standard, on where these files are resolved from. Could you generate your editorconfig file...

Well, I guess it's worth clarifying that kotlinter-gradle does allow some properties to be configured in the gradle file, see here: https://github.com/jeremymailen/kotlinter-gradle#configuration Which configuration properties did you need to customize?

Ok, one style is now documented in the readme and it seems like people have ways to target the files they want. Closing for now.

These behaviors are at the code level so I believe this is `ktlint` functionality. I assume if you run the `ktlint` cli you get the same results?

Going ahead and closing this as this behavior is implemented by `ktlint` itself. If there's a big over there we'll need to file a issue against ktlint.

That is correct, a task exists for each SourceSet, so you need to customize them as shown here https://github.com/jeremymailen/kotlinter-gradle#customizing-tasks As with all things gradle you can programmatically iterate through tasks...

That's what I was thinking. Do note when you are excluding file paths above the package root, you need to use a slight different incantation to exclude the path. Two...

I agree, we should document a simple example like that to help people so they don't need to go digging. This would be a great little PR for someone to...

I recommend using the git hooks that come with ktlint actually since a command line invocation makes a lot more sense in a git workflow. Likely hooks will be phased...