-
Notifications
You must be signed in to change notification settings - Fork 418
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
Dump DokkaConfiguration as JSON when running with the debug logging level #2873
Comments
Could this be done at a runner level? I have a couple of suggestions for dumping the config file in the Gradle plugin.
|
@aSemy something like that could indeed be implemented as an intermediate solution 👍 The simplest way I can think of is #3008, please have a look if it's enough for now, I'll be able to cherry-pick it into 1.8.20 Opening up I'd still like a better way to be added when we have time, so that there's no need to add custom tasks or build logic as not everyone is proficient with Gradle. Ideally, it should be as simple as "add this one line/env property, run Dokka and attach all files from that directory" - would help with diffs, too (everyone will "the same" files as opposed to slightly differently configured tasks). |
Fixed in Dokka 2.0.0 in Dokka Gradle plugin v2 |
When Dokka is run with the debug logging level via Gradle/Maven/CLI runners, it should dump a pretty-printed JSON string of the used
DokkaConfiguration
.This would be very helpful when debugging various user problems as a lot of the times bugs occur due to invalid configuration.
This would also help with comparing configurations across projects/versions and allow us to manually check the compatibility on configuration level.
The text was updated successfully, but these errors were encountered: