Kotlin on Code Quality Tools
summary
Compares Android Lint, Detekt and ktlint with concrete tradeoffs: ktlint autoformats via -F and editorconfig and is fastest; Detekt runs YAML-configured static checks, reports in Checkstyle/XML/HTML and estimates fix time but has no autoapply; Android Lint supports type resolution, IDE quickfixes and a Gradle lintfix task, is slower but more powerful and supports baselines via a baseline file. Shows building a no-internal-import rule for each tool, how rules register (service/issue registry/UAST visitors), and how to run them in CI.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:27Why use code quality tools
- 3:58Available tools overview
- 6:24Android Lint basics
- 9:17Baseline with Android Lint
- 10:40Android Lint auto-fix
- 12:26Detect setup and usage
- 15:11KTLint setup and usage
- 17:17Adding custom rules
- 23:56Custom rules in projects
- 29:56Resources and community
- 33:06Tool comparison and Q&A
related talks
22mKotlin on Code Quality Tools
41mKotlin Static Analysis with Android Lint
42mSafe(r) Kotlin Code - Static Analysis Tools for Kotlin
24mImprove your code with Lint checks for Kotlin
19mEase Software structural quality on Android (en)
37mStatic Code Analysis For Kotlin
20mClean Code Base: Harnessing the Power of Android Lint and Custom Rules
44mLint. What, Why, How?
