Android: Quality tools

[CedrickFlocon]

As all open source project we need to add quality tools.
It's an open discussion to find out the best setup.

e.g.
SonarQube
Detekt
Klint

[marciogranzotto]

I'm not very familiar with SonarQube or Detekt, but where Ktlint shines for me is that it follows the official Kotlin guidelines and there's no much configuration to be done.

For reference, as said on this article:

Ktlint gives you less stuff to discuss. It follows the official style. When you let the lint too open for configuration, people create their “official” style, as happened to eslint. Too many style guide versions can lead to inconsistency and counterproductive discussions.

[CedrickFlocon]

In my point of view we could use SonarQube for code coverage, bug and code smell.
And KLint for formating.

[marciogranzotto]

Makes sense. I'll update my ktlint branch with the master changes and reopen the PR so we can get this part done. Then we can add another PR for SonarQube later.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.