If somebody is aware of a workaround for <https://...
# dokka
If somebody is aware of a workaround for https://github.com/Kotlin/dokka/issues/2913 which impacts Spring Framework Kotlin documentation, feel free to share. Otherwose I hope Dokka team will be able to fix this.
I'll have a closer look as soon as I have time Preliminary thoughts: I think Dokka is getting confused with packages. It sees that the package is the same for the page you're referencing, and it sees the referenced class is on the classpath, so it might be thinking that the page must exist as well, whereas it's actually supposed to be an external link
Yep that my understanding as well. I hope a check it exists otherwise fallback on external link configured enhancement could be made.