This PR fixes the doc generation, broken since 3.4.0.
JavaDoc does not like Kotlin, so we are updating it to a more modern documentation framework, Dokka. We are adding also a new flow to upload the documentation to the GitHub pages.
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
[X] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Edit the title of this pull request with a semantic commit prefix (e.g. "fix: "), which is necessary for automated release workflows to decide whether to generate a new release and what type it should be.
[ ] Will this cause breaking changes to existing Java or Kotlin integrations? If so, ensure the commit has a BREAKING CHANGE footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
This PR fixes the doc generation, broken since 3.4.0.
JavaDoc does not like Kotlin, so we are updating it to a more modern documentation framework, Dokka. We are adding also a new flow to upload the documentation to the GitHub pages.
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
BREAKING CHANGE
footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/Fixes #1248 🦕