Categories
Latest version
v0.11.1
Updated on
May 7, 2024
Total issues
81
Autofix
10
Sample configuration
version = 1
[[analyzers]]
name = "kotlin"
[analyzers.meta]
language_version = "1.8"
runtime_version = "17"
Stats
Anti-pattern
48
Bug risk
24
Documentation
1
Performance
5
Style
3
Method should not throw exceptions KT-W1056
Avoid throwing exceptions in non-fallible operations such as equals() or toString().
The range specified for iteration is empty KT-W1031
It is important to ensure that ranges specified in for loops are valid. Ranges that are empty can lead to unexpected behavior.
Map values fetched with not-null assertion operator KT-W1034
Using the not-null assertion operator (!!) along with the index operator [] or the .get() method of a map type can result in a NullPointerException if the key is not present in the map. This is because Map.get() returns null if the key is not found. By using the not-null assertion operator, you are explicitly telling the compiler that the result will never be null, which can lead to a runtime exception if the assumption is incorrect.
File location does not match the declared package KT-W1044
Having the file location not matching the declared package is considered bad practice in software development. It can lead to confusion, make code harder to locate and navigate to, hinder collaboration among team members, cause issues with build systems and tools, reduce code portability and reusability, and negatively impact code
Avoid using forEach with ranges KT-P1000
Using the forEach method on ranges has a heavy performance cost. Prefer using simple for loops.