hands_on_kotlin VS ktlint

Finally, we apply this configuration to all our subprojects by adding the below inside our project-level build.gradle

We can now access the methods for signing in with Google. Let’s create a class (GoogleApiContract) that is responsible for calling the google APIs

In our previous articles, we managed to create our TodoApp. Now, let's write some tests.

TodoItem (Our entity class)

Source code.

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: