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
Add flag to hide all inherited members #1501
Comments
Came here from this SO post. Would love to see this make it through sometime soon. Thanks for the awesome tool! |
Has this important issue addressed yet? Been 6 months! It makes dokka completely unusable for Android projects with hundred of functions inherited. The functions I defined in the class are impossible to find and very cluttered. Details: #1780 |
In our project, we ended up using the This puts all the inherited junk into a separate tab at least, see an example here Only a solution for the HTML output, and not the best possible solution, but it's something. |
@zsmb13 Thank you! got it working. Had to change configuration a little from your getstream example. I had to use this for dokka v1.4.30
But still hoping for more flexible solution by the dokka maintainers as it only works with HTML as you mentioned. |
Oh yes, the task to modify depends on whether you use multi module dokka or not, either dokkaHtml or dokkaHtmlPartial. |
This should be fixed in |
I mixed up issues. The comment above was meant for #1779 |
How does the v1.4.30 fixes it? How should we use the @hpehl Can you please show how you tried that with example? |
Fake overrides should be filtered out by default in |
@shipsywor sorry I mixed up issues. When I claimed that is was fixed I was referring to #1779 not this issue. |
@kamildoleglo On Version 1.4.30, the result is still not as desired. I have created a sample project here: https://github.com/shipsywor/dokka-android-kotlin-sample As you stated, fake overrides should be filtered by default BUT they are not. Everything except |
I think that there is a little bit of a confusion around what |
For whoever lands on this page in the future and would like to avoid the mini rabbit hole I went through: The solution that the PR in late March introduced was to configure your dokka task to set |
Above discussion did not resolve it for me.
Using dokka version 1.6.10 |
There should be possibility to hide all inherited (aka
FAKE_OVERRIDEN
) members of classThe text was updated successfully, but these errors were encountered: