You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typealiases have their own dedicated pages since Dokka 1.9.0 (#2862). It's a relatively new enhancement, so this particular issue likely slipped unnoticed and we didn't think of this use case, but it's not necessarily regression.
Expected
The dedicated page should either contain extension functions for typealiases or it should not, but either way there should be no empty tabs. Either no extension and no tab, or extensions under a tab.
Actual
The Members & Extensions tab is rendered, but there's no content, so the tab is empty.
Screenshot
Reproducer
Generate documentation for the following code and visit the page for TypeAliasToMyClass.
Hey! As a library author, I think having the ability to view extension functions declared on a typealias in its dedicated page would be very useful.
I often use type parameters and extension functions to restrict usage of some functionality to some specific situation, as described by the type parameter. Because this can become unwieldy quickly, I create typealiases for these situations. It would be great if users could open a typealias' page and immediately see all the functionality that typealias is responsible for.
Context
Typealiases have their own dedicated pages since Dokka 1.9.0 (#2862). It's a relatively new enhancement, so this particular issue likely slipped unnoticed and we didn't think of this use case, but it's not necessarily regression.
Expected
The dedicated page should either contain extension functions for typealiases or it should not, but either way there should be no empty tabs. Either no extension and no tab, or extensions under a tab.
Actual
The
Members & Extensions
tab is rendered, but there's no content, so the tab is empty.Screenshot
Reproducer
Generate documentation for the following code and visit the page for
TypeAliasToMyClass
.The text was updated successfully, but these errors were encountered: