“Kotlinlang” style is 4/4 indents, “Java-like” is 2/4 spaces. (Block / continuation respectively). There’s another style, “google” which I didn’t expose in the website but is available in ktfmt, that does 2/2 spaces.

@Big Chungus I totally agree. I just stated I loathe 4 spaces, it’s a ridiculous default. I don’t get the “interop with java”. It makes no sense. We don’t write Java in Kotlin code nor the other way around. Even if you have a mixed project, a simple

.editorconfig

solves this problem. I am in the 2 space camp and will always be. I also don’t use

;

in my javascript, nor does my team. 😄 If we want kotlin to look like Java, the write Java. Or, start using semicolons on everything. Don’t use type inference, don’t use external functions or extension functions, or Kotlin features. If you want the Java look and feel, use Java. The worst was the Sun Java coding conventions. Go look at that original source from 1.1. That’s a hot mess.

Example here. That

fillMode

assignment here is broken up into yet another line because it’s at column 20 where it could have been at 10. That makes things harder to read. Not to mention that code should be extracted. Too many if statements in a loop. Too hard to test. That’s off topic. But anyway. all just my opinion.

Anyway, the solution is to enforce tabs. Using tabs everyone can have the size they prefer.

Sharing the ktfmt config file in git has another advantage, when you clone the project if you have the plugin installed or you install it, it will be enabled for that project

I don't know if that behavior should be replicated if a .editorconfig exists and ktfmt read it to detect which format should use. Probably it is not a good idea