rnett
08/09/2025, 11:47 PM[my-module]
), relative links to the directory ([my-module](./my-module)
), and relative HTML links ([my-module](../my-module/index.html)
), none of which work. The second two are rendered as the link address rather than being links.Oleg Yukhnevich
08/11/2025, 10:57 AMAdam Semenenko
08/11/2025, 12:01 PM<a href="../../../childProjectA/index.html">Link to module a</a>
working for meAdam Semenenko
08/11/2025, 12:01 PMOleg Yukhnevich
08/11/2025, 12:04 PMrnett
08/11/2025, 9:13 PM[symbols-kotlin-compiler](/symbols-kotlin-compiler/index.html)
? Because that's not working either. Or do you mean an <a>
element?rnett
08/11/2025, 9:15 PM./my-module
, where dokka would figure out if that there is a module included corresponding to that directory and turn it into a link (and error if it can't find one).Oleg Yukhnevich
08/11/2025, 9:33 PM[core](<https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core>)
My ideal solution would be relative links to the sub-module directories in the projectA better idea might be to support default markdown links to files, and if links point to other module doc, Dokka can replace them during generation (or throw a warning) In this case, both IDEs, GitHub, and Dokka will recognize those links. I haven't found an issue specific to module-to-module links, so it would be nice if you leave your use-case/how/why you will use it: https://github.com/Kotlin/dokka/issues/1863
rnett
08/12/2025, 12:22 AMrnett
08/12/2025, 12:46 AM