Following the article <https://kt.academy/article/...
# getting-startede
Edgar Avuzi
04/21/2025, 4:05 PMFollowing the article https://kt.academy/article/ek-platform-types Summary section
> Types that come from another language and have unknown nullability are known as platform types.
> Since they are dangerous, we should eliminate them as soon as possible and not let them propagate.
> It is also good to specify types using annotations that specify nullability for exposed Java constructors, methods and fields.
> This is precious information for Java and Kotlin developers who use these elements.
specifically
> Since they are dangerous, we should eliminate them as soon as possible and not let them propagate.
How can one enforce — perhaps during build time — that any Java platform type must be explicitly resolved at the first point of Java ↔️ Kotlin interaction, so that no platform types leak deeper into the Kotlin codebase? Without modifying the Java code
e
ephemient
04/21/2025, 4:11 PMm
Michael Krussel
04/21/2025, 4:17 PMYou could also use
https://detekt.dev/docs/rules/potential-bugs/#hasplatformtype
👍 1
e
Edgar Avuzi
04/21/2025, 4:22 PMthank you