Vadim Mishenev

The summary based on the spike https://github.com/Kotlin/dokka/issues/3576: Presumably we decided to show a backing field, a getter, and a setter always. We are going to ask to validate our decision...

Related issues: https://github.com/Kotlin/dokka/issues/3317 https://github.com/Kotlin/dokka/issues/3513 Thank you for the reproducer. --- The problem is that the Dokka Gradle Plugin wrongly(?) defines `jvmAndAndroid` as a common platform [here](https://github.com/Kotlin/dokka/blob/d4d457d357627fd8100e4f0d47868020485996ec/dokka-runners/runner-gradle-plugin-classic/src/main/kotlin/org/jetbrains/dokka/gradle/kotlin/KotlinSourceSetGist.kt#L24). That means that: ```kt...

The compiler provides the ability to call methods through Kotlin types that are not declared in them, but are present in platform Java types. There are 3 kind of declarations...

The list of such functions with their status is [here](https://github.com/JetBrains/kotlin/blob/0ef41d75b5901afea68a09cc3e762b52d8ce1e3c/core/compiler.common.jvm/src/org/jetbrains/kotlin/builtins/jvm/JvmBuiltInsSignatures.kt#L15). The list of mapped types is [here](https://github.com/JetBrains/kotlin/blob/bb044bb57ebf2f9fffcf63391e06c007738dd72e/core/compiler.common.jvm/src/org/jetbrains/kotlin/builtins/jvm/JavaToKotlinClassMap.kt#L53) In K2, there is a [class](https://github.com/JetBrains/kotlin/blob/624bea3ecf1e027454f39b4c2a4843ba6c426be8/compiler/fir/java/src/org/jetbrains/kotlin/fir/scopes/jvm/JvmMappedScope.kt#L55) that is responsible for providing a mapped...

Dokka should filter out filter out such methods from documentation since: 1. they have no available doc; 2. In K1, we experience some inconsistencies during the analysis of stdlib. For...

Although types from Java are flexible-nullable in Kotlin, Dokka does not support such types—`String!` (at least for Documentable). Currently, the nullable `String?` seems to be a more accurate way to...

Was your project compiled successfully? Otherwise, it looks like https://github.com/Kotlin/dokka/issues/2171#issuecomment-928967963

[Dokka 2.1.0](https://github.com/Kotlin/dokka/releases/tag/v2.1.0) has been released with K2 analysis enabled by default. It fully supports Kotlin/JVM and KMP projects. There are no known blockers that would force users to fall back...

```kt fun x(){} /** * ref to [x] */ val x = 0 ``` In K1 the `[x]` leads to `fun x`. In K2 it leads **only** to the property....

K2 behavior for factory functions: ```kt /** * [SomeCl] leads to the class */ class SomeCl(i: Int) /** * [SomeCl] leads to the factory function * In K1, it leads...