Whether to skip documentation generation.
Default: false
The display name used to refer to the project/module. It's used for the table of contents, navigation, logging, etc.
Default: {project.artifactId}
The directory to where documentation is generated, regardless of format.
Default: {project.basedir}/target/dokka
Whether to fail documentation generation if Dokka has emitted a warning or an error. The process waits until all errors and warnings have been emitted first.
This setting works well with reportUndocumented.
Default: false
Whether to suppress obvious functions.
A function is considered to be obvious if it is:
kotlin.Any, Kotlin.Enum, java.lang.Object or
java.lang.Enum, such as equals, hashCode, toString.
dataClass.componentN or dataClass.copy.
Default: true
Whether to suppress inherited members that aren't explicitly overridden in a given class.
Note: This can suppress functions such as equals/hashCode/toString,
but cannot suppress synthetic functions such as dataClass.componentN and
dataClass.copy. Use suppressObviousFunctions for that.
Default: false
Whether to resolve remote files/links over your network.
This includes package-lists used for generating external documentation links. For example, to make classes from the standard library clickable.
Setting this to true can significantly speed up build times in certain cases,
but can also worsen documentation quality and user experience. For example, by
not resolving class/member links from your dependencies, including the standard library.
Note: You can cache fetched files locally and provide them to
Dokka as local paths. See externalDocumentationLinks section.
Default: false
The source code roots to be analyzed and documented.
Acceptable inputs are directories and individual .kt / .java files.
Default: {project.compileSourceRoots}
The set of visibility modifiers that should be documented.
This can be used if you want to document protected/internal/private declarations,
as well as if you want to exclude public declarations and only document internal API.
Can be configured on per-package basis.
Default: PUBLIC
Whether to emit warnings about visible undocumented declarations, that is declarations without KDocs
after they have been filtered by documentedVisibilities and other filters.
This setting works well with failOnWarning.
This can be overridden at package level.
Default: false
Whether to document declarations annotated with @Deprecated.
This can be overridden at package level.
Default: false
Whether to skip packages that contain no visible declarations after various filters have been applied.
For example, if skipDeprecated is set to true and your package contains only
deprecated declarations, it is considered to be empty.
Default: true
The directories or individual files that should be suppressed, meaning that declarations from them are not documented.
The JDK version to use when generating external documentation links for Java types.
For example, if you use java.util.UUID in some public declaration signature,
and this option is set to 8, Dokka generates an external documentation link
to JDK 8 Javadocs for it.
Default: JDK 8
The Kotlin language version used for setting up analysis and @sample environment.
By default, the latest language version available to Dokka's embedded compiler is used.
The Kotlin API version used for setting up analysis and @sample environment.
By default, it is deduced from languageVersion.
Whether to generate external documentation links that lead to the API reference documentation of Kotlin's standard library.
Note: Links are generated when noStdLibLink is set to false.
Default: false
Whether to generate external documentation links to JDK's Javadocs.
The version of JDK Javadocs is determined by the jdkVersion option.
Note: Links are generated when noJdkLink is set to false.
Default: false
A list of Markdown files that contain module and package documentation
The contents of specified files are parsed and embedded into documentation as module and package descriptions.
The classpath for analysis and interactive samples.
This is useful if some types that come from dependencies are not resolved/picked up automatically.
This option accepts both .jar and .klib files.
Default: {project.compileClasspathElements}
A list of directories or files that contain sample functions which are referenced via @sample KDoc tag.
The path to the local source directory. The path must be relative to the root of the current module.
The URL of the source code hosting service that can be accessed by documentation readers, like GitHub, GitLab, Bitbucket, etc. This URL is used to generate source code links of declarations.
The suffix used to append source code line number to the URL. This helps readers navigate not only to the file, but to the specific line number of the declaration.
The number itself is appended to the specified suffix. For example, if this option is set
to #L and the line number is 10, the resulting URL suffix is #L10.
Suffixes used by popular services:
#L#L#lines-
The root URL of documentation to link to. It must contain a trailing slash.
Dokka does its best to automatically find the package-list for the given URL,
and link declarations together.
If automatic resolution fails or if you want to use locally cached files instead,
consider setting the packageListUrl option.
The exact location of a package-list. This is an alternative to relying on Dokka
automatically resolving it.
Package lists contain information about the documentation and the project itself, such as module and package names.
This can also be a locally cached file to avoid network calls.
The regular expression that is used to match the package.
Default: .*
Whether this package should be skipped when generating documentation.
Default: false
The set of visibility modifiers that should be documented.
This can be used if you want to document protected/internal/private declarations within this package,
as well as if you want to exclude public declarations and only document internal API.
Default: PUBLIC
Whether to document declarations annotated with @Deprecated.
This can be set on project/module level.
Default: false
Whether to emit warnings about visible undocumented declarations, that is declarations without KDocs
after they have been filtered by documentedVisibilities and other filters.
This setting works well with failOnWarning.
Default: false