-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
How can we propagate inherited functionality documentation without __pdoc__
?
#295
Comments
Hi there! Generally speaking pdoc really intends to document your API as it is, but there may be a few exceptions where what you are looking for makes sense (you mentioned mixins on Slack). pdoc/pdoc/templates/default/module.html.jinja2 Lines 789 to 811 in 4bce7e2
If you change the access from |
Thanks @mhils for the prompt response! Very elegant solution. Closing this issue. |
Problem Description
Greetings! I am a new user of
pdoc
, it's so easy to use!I have a system with multiple inheritance, I would like all inherited functionality to be documented in the child class. If
__pdoc__
still existed, I think this would be possible, but in light of its currently suspended support, is there a solution for this?code example
Suppose we have this class hierarchy:
I would like the documentation of
C
to render as if I had something like:Is this possible right now?
Proposal
None. This is more of a question.
Alternatives
I guess one alternative is to use the system as is, with inherited members. But I would like to view everything on the same page without changing the structure of my library.
Additional context
None
The text was updated successfully, but these errors were encountered: