-
Notifications
You must be signed in to change notification settings - Fork 473
Dokka: Generate aggregated API docs #691
Comments
I wasn't able to come up with a satisfying solution on Friday. The only thing about generating a multi module documentation is this issue in the dokka repository: One of the mentioned solutions is to create a module just for generating the documentation and letting this module depend on all other modules. This sounds like it's too hacky for us and I was trying to avoid this. I pushed my state here: This branch does:
It does not:
Also: telemetry has a different package layout and looks a bit weird in that mix: #698. |
Dokka has a classpath parameter:
I assume that setting this to the "classpath" needed to compile the modules would resolve the issue of unknown classes. However I was unable to build this classpath dynamically. Another thing I tried was adding GeckoView as a dependency to |
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
I managed to solve this by dynamically constructing the classpath. The main piece of the puzzle was |
@csadilek Awesome. Well done :) |
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Currently we create separate API docs for all modules. Because of that you can't jump between modules in the documentation. For example if you are on the page about
GeckoEngine
you can't get toEngine
because this class is in a different module.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: