Andrey Tyrin

Since we are here, could you adjust the contribution guide regarding the new way of running/excluding integration tests? And probably GitHub workflows (if it required)?

JIC: A usage in the wild (if someone had doubts): https://github.com/square/okhttp/blob/0343ff823c17357c8e1994b4c0f0ea783dcace7a/mockwebserver/src/main/kotlin/mockwebserver3/SocketPolicy.kt#L83 In this case (nested class), with K2, we generate an incorrect link to the property. `http://localhost:63342/okhttp-parent/k2/mockwebserver3/mockwebserver3/-socket-policy/-do-not-read-request-body/--root--.html` instead of `http://localhost:63342/okhttp-parent/k2/mockwebserver3/mockwebserver3/-socket-policy/-do-not-read-request-body/http2-error-code.html`

One more point. It affects also references in the class body: ```kotlin class ClassWithLongSeeAlsoList(val propInPrimaryConstructor: String) { val propInBody: String = "" /** * Adds a [propInPrimaryConstructor] to this group....

Maybe this one could be a side effect of #3558

Also noticed: with K2 pages.json (responsible for search) `vararg` option is missed.

JIC: https://youtrack.jetbrains.com/issue/KT-61988/Wasm-common-sharing-code-between-wasm-targets

Just in case: the settings passed to `` are used by Dokka during documentation generation. But IJ is unable to recognize the relevant nodes in `pom.xml`, and the building process...

A similar issue for `Exception` inheritors. For example, the class declaration in `commonMain`: ```kt // stdlib part public expect open class RuntimeException : Exception { public constructor() public constructor(message: String?)...

Should be. If there is a parameter, then it works. The issue is only for implicit constructors.

For `DokkaMultiModuleTask` and `DokkaCollectorTask` tasks Dokka has API methods for adding and removing child tasks (`addChildTask(s)`/`removeChildTask(s)`, `addSubprojectChildTasks`/`removeSubprojectChildTasks` ). These methods may accept path/task/project as a parameter. The list of such...