I have `dokkaGfmMultiModule` working well for me ...
# dokka
b
I have
dokkaGfmMultiModule
working well for me for the most part, only complaint is that right now I’m getting an extraneous module directory for each module, so if I have a
moduleA
, I get:
Copy code
- docsRoot
  - moduleA
    - moduleA
      - package-list
      - [etc]
    - index.md
Is that intended?
Root level config is just
Copy code
dokkaGfmMultiModule {
    outputDirectory = file("docs/api")
  }
Module level config:
Copy code
dokkaGfmPartial {
    dokkaSourceSets {
      named("main") {
        def docFiles = ["module.md", "packages.md"]
        docFiles = docFiles.findAll { project.file(it).exists() }

        reportUndocumented.set(false)
        skipDeprecated.set(true)
        jdkVersion.set(8)
        includeNonPublic.set(false)
        includes.from(docFiles)
      }
    }
}
m
Do you have any nested modules? This behaviour is expected for them since we would like to preserve project’s structure to avoid issues with conflicting file names 😄 For a stock project i get something like this for 1.4.32:
b
The source modules are nested, but not under folders of the same name (eg
group/moduleA
, not
moduleA/moduleA
)
And to be clear- that grouping is being maintained (I have
group/moduleA/moduleA/index.md)
.
Is it at all possible to disable or override this behavior?
m
I don’t think so, but is it a problem? All links should work fine
b
It's not a huge problem, but it does break links that are out there from before enabling multimodule, and it also makes links unnecessarily longer (and those longer links look incorrect)