Autostyle can format <java | kotlin | scala | sql | groovy | javascript | flow | typeScript | css | scss | less | jsx | vue | graphql | json | yaml | markdown | license headers | anything> using <Gradle>.

• Autostyle for Gradle 5.6+
• Other build systems

Ideally, a code formatter can do more than just find formatting errors - it should fix them as well. Such a formatter is really just a Function<String, String>, which returns a formatted version of its potentially unformatted input.

It's easy to build such a function, but there are some gotchas and lots of integration work (newlines, character encodings, idempotency, and build-system integration). Autostyle tackles those for you so you can focus on just a simple Function<String, String> which can compose with any of the other formatters and build tools in Autostyle' arsenal.

Why are there empty squares? Many projects get harder to work on as they get bigger. Autostyle is easier to work on than ever, and one of the reasons why is that we don't require contributors to "fill the matrix". So far Autostyle works better with Gradle, however we would consider PRs even if it only supports the one formatter you use.

And if you want to add FooFormatter support, we'll happily accept the PR even if it only supports the one build system you use.

Once someone has filled in one square of the formatter/build system matrix, it's easy for interested parties to fill in any empty squares, since you'll now have a working example for every piece needed.

• Thanks to contributors of Spotless.
• Built by Gradle.
• Tested by JUnit.
• Maintained by Vladimir Sitnikov.