Vadim Mishenev
Vadim Mishenev
I have created [KT-65110](https://youtrack.jetbrains.com/issue/KT-65110/Analysis-API-In-Standalone-mode-the-order-of-symbols-is-unstable) to have a stable order internally.
I have opened [KT-56838](https://youtrack.jetbrains.com/issue/KT-56838/JavaMethodDescriptor.overriden.overriden-has-an-incorrect-value-for-inherited-methods-of-Java-collections)
[KT-56838](https://youtrack.jetbrains.com/issue/KT-56838/JavaMethodDescriptor.overriden.overriden-has-an-incorrect-value-for-inherited-methods-of-Java-collections) is not a bug, it's a feature. It happens because of [Java mapping](https://kotlinlang.org/docs/java-interop.html#mapped-types). For our case: `kotlin.collections.AbstractMutableCollection -> java.util.AbstractCollection -> MutableCollection (mapped to java.util.Collection) -> Collection (also mapped to...
Related issue: #3054
In Dokka 1.9.0 typealiases will have their own separate pages, so they will be clickable. Also, the search of typealises will be fixed.
**Note** Both cases do not work in IDE K1:   They lead to an internal error in IDE: 
There is a problem in a parser of compiler (PSI). see https://github.com/JetBrains/kotlin/blob/master/compiler/psi/src/org/jetbrains/kotlin/kdoc/lexer/KDoc.flex  There is a workaround on Dokka's side: to resolve KDoc links like in K1.
KMP projects can also be used for testing since almost all issues have been fixed in #3137.
It is blocked by https://github.com/Kotlin/dokka/issues/2881
It is related to https://github.com/Kotlin/dokka/issues/3338#issuecomment-2112381563 Also, we decided to not distinguish the `protected` keyword between Kotlin and Java since it seems the use case when an Java declaration is externally...