Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to Kotlin API Is Broken (404) #42

Closed
philipbel opened this issue Sep 25, 2019 · 3 comments
Closed

Link to Kotlin API Is Broken (404) #42

philipbel opened this issue Sep 25, 2019 · 3 comments
Assignees
Labels
status/has-workaround This has a known workaround described type/bug A general bug

Comments

@philipbel
Copy link

Expected Behavior

On the Documentation page, the Kotlin Doc should show the Kotlin API.

Actual Behavior

The link shows a 404.

Steps to Reproduce

  1. Open the Documentation page.
  2. Click on the Kotlin Doc link under Reactor Core / Javadoc.
@simonbasle
Copy link
Member

Thanks for reporting this. I'll remove the link to kotlin docs in the core section, since the extensions have now been extracted into a separate project (see the release notes).

Unfortunately, please note that we're unable to publish KDoc at this time due to a bug in the Dokka tool. See reactor/reactor-kotlin-extensions#3

@simonbasle simonbasle self-assigned this Sep 25, 2019
@simonbasle simonbasle added status/has-workaround This has a known workaround described type/bug A general bug labels Sep 25, 2019
@simonbasle
Copy link
Member

In the meantime, please refer to the javadoc version of kotlin extensions: https://projectreactor.io/docs/kotlin/release/api/

@philipbel
Copy link
Author

Thanks for the info, Simon!
Not a huge issue; just not nice getting a 404.

simonbasle added a commit that referenced this issue Sep 25, 2019
 - Removed the Kotlin Doc link from core and test sections
 - Replaced the Kotlin Doc link in kotlin-extensions section with
 javadoc link (see reactor/reactor-kotlin-extensions#3)
 - DocUtils takes these restrictions into account and we now redirect
 to a special 404 page to explain the situation, should one directly
 request a bad kdoc-api link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/has-workaround This has a known workaround described type/bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants