I have `dokkaGfmMultiModule` working well for me for the most part, only complaint is that right no...

# dokka

[Bryan Herbst]

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:

- docsRoot
  - moduleA
    - moduleA
      - package-list
      - [etc]
    - index.md

Is that intended?

[Bryan Herbst]

Root level config is just

dokkaGfmMultiModule {
    outputDirectory = file("docs/api")
  }

Module level config:

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)
      }
    }
}

[Marcin Aman]

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:

[Bryan Herbst]

The source modules are nested, but not under folders of the same name (eg group/moduleA, not moduleA/moduleA)

[Bryan Herbst]

And to be clear- that grouping is being maintained (I have group/moduleA/moduleA/index.md).

[Bryan Herbst]

Is it at all possible to disable or override this behavior?

[Marcin Aman]

I don’t think so, but is it a problem? All links should work fine

[Bryan Herbst]

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)