-
Notifications
You must be signed in to change notification settings - Fork 409
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
Extension functions and properties defined for base classes and interfaces #1908
Comments
Diff here is between https://github.com/msink/kotlin-libui/blob/dokka/docs/libui.ktx/-box/README.md - generated years ago by Dokka 0.9.17, and https://github.com/msink/kotlin-libui/blob/dokka/dokka/libui.ktx/-box/README.md - generated by task MyGfm is modified version of Gfm renderer, in |
Yes, but do you mean that we no longer display extension functions and properties on the receiver's page ? |
I see that extension functions now are displayed only directly for class/interface for what they are defined. |
Looks as |
No, they are inherited. In the following example:
Documentation generated for |
Don't know, as was said in first message, in my use case:
documentation generated for |
Ok, i get the reasoning now. To be fair this is quite an tough topic that i don't have a solution for. In newer dokka we decided to have extensions rendered where they are declared and only add those to the classes that they are for. We didn't include any inheritance there simply because it is quite impossible to draw a line what you should and shouldn't render (extensions on Any, how do you view all of those functions, effective searching, extensions in different modules, visibilites, UX on gfm/html etc). I'll convert this to an enhancement since current behaviour is an expected one but will try to at least come up with a solution on how to tackle it as it might be needed for stable release |
Show all functions, but render them further down on the page and weight them lower for searching depending on how far removed they are from the type? Or list them all in one compact block? |
Extensions that are defined in the application may be relevant for all child classes as well. Are these included in the 'Inherited functions' or 'Inherited properties' tabs, when configuration 'separateInheritedMembers= true' ? |
It can be useful for Although for |
Describe the bug
Extension functions and properties defined for base classes and interfaces - are lost.
For example (a bit simplified):
Diff for what was generated by Dokka 0.9.17 and Dokka 1.4.32:
Expected behaviour
Not sure, but maybe add new sections "Inherited extension functions" and "Inherited extension properties"
But anyway - not just lose it.
To Reproduce
https://github.com/msink/kotlin-libui/tree/dokka
The text was updated successfully, but these errors were encountered: