Check for === instead of ==

[rockwotj]

Expected Behavior of the rule

Prevent usage of instance equality checks

Context

=== and == are both valid in kotlin. We also write a lot of typescript/javascript on our team (sadly no multiplatform kotlin) and a few of us accidently use === sometimes instead of == for equals. There should be a rule to prevent usage of === as you very rarely want instance equality checks anyways.

[schalkms]

I suggest to create a custom rule here. Detekt tries to include rules that are relevant for the majority of the user base. IntelliJ also doesn’t flag the mentioned use case. If you have a lot of TypeScript developers in your team, a custom rule is the way to go.

https://detekt.github.io/detekt/extensions.html#custom-rulesets

[rockwotj]

I think not using === is common to everyone, it just comes up frequently for us. Still, a custom rule it is

[schalkms]

I think not using === is common to everyone

If you want to check the referential equality of two objects in Kotlin, you should use the === operator.
Please remember that this rule would also flag valid use cases for referential equality checks. Then the programmer could only add a suppress annotation to get rid of the warning.

it just comes up frequently for us

That's completely okay. Different teams have different needs and use cases. For that reason, detekt includes the possibility to write a custom rule. In this case, it should be fairly easy.
For questions related to custom rules please feel free to post a message.