ktlint VS kotlin-android-template

In my experience, I have faced these issues while trying to keep the code style consistent across the team - 1. ktlint and "Reformat Code" in Android Studio produce different outputs. This causes issues as most developers find it easier to use "Reformat Code" in AS but if you have a ktlint check on CI, the checks sometimes fail. 2. Different AS versions produce different `codeStyles.xml` file. Sometimes, on updating AS, it automatically adds new rules to the `codeStyles.xml` file. These rules might not be compatible with ktlint and might only work on specific AS versions.

Ktlint

Not even an Android Studio-specific feature, but rather a feature of the underlying IntelliJ. Just select Code > Analyze code > Silent code cleanup and your entire project will be cleaned up using the default linter (this can be combined awesomely with Ktlint).

Ktlint + Detekt: Kotlin linting/static analysis (https://ktlint.github.io, https://detekt.github.io/detekt)

Refs. Klint Page Klint Github

Linting is the process of analyzing code for potential errors and one of the ways we can do that in Kotlin is using Ktlint. As per the documentation:

This happened to me all the time when I wanted to create a new project on my own and it's something that should have a solution to improve the development speed. That's why I researched on the internet and found some examples about it like this. There were plenty of it but no one fit for me since most of them were oriented to use MVP and I'm more into MVVM. That's why I decided to create my own template on github