Skip to content

misc: upgrade to Dokka 2.0.0 #1284

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

Open
wants to merge 19 commits into
base: main
Choose a base branch
from
Open

misc: upgrade to Dokka 2.0.0 #1284

wants to merge 19 commits into from

Conversation

lauzadis
Copy link
Contributor

Issue #

Description of changes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This comment has been minimized.

@lauzadis lauzadis marked this pull request as ready for review May 15, 2025 22:31
@lauzadis lauzadis requested a review from a team as a code owner May 15, 2025 22:31

This comment has been minimized.

1 similar comment
Copy link

Affected Artifacts

No artifacts changed size

@@ -0,0 +1,30 @@
import kotlin.text.set
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: I like the idea of refactoring this out of the main build file. How much more work would it be to move it all the way out into aws-kotlin-repo-tools so that we had less duplication?

Comment on lines -96 to -101
// Output subprojects' docs to <docs-base>/project-name/* instead of <docs-base>/path/to/project-name/*
// This is especially important for inter-repo linking (e.g., via externalDocumentationLink) because the
// package-list doesn't contain enough project path information to indicate where modules' documentation are
// located.
fileLayout.set { parent, child ->
parent.outputDirectory.dir(child.moduleName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does dokka handle this now or is the layout going to change?

Comment on lines +77 to 79
dependencies {
dokka(project(":runtime"))
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this now?

* Ensure `navButton` elements are interactable and have proper accessibility properties
* Fixes accessibilty violation: "Ensure all interactive functionality is operable with the keyboard"
*/
function ensureNavButtonInteractable() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this built-in in dokka 2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants