-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Inherited menber #138
Comments
Hello! Thanks for your help! Erm, I had started working on it but can't find my local branch anymore... probably on another computer. Will let you know 🙂 |
Great then ! |
So, I never found the branch I was talking about, hahaha... 💀 |
I would be happy to do this PR. I found a hack on my side which is why I did not spend much time on this for now |
Quick question: how would you then render inherited members in your docs? Like this? ::: path.to.my.Class
options:
inherited_members: true Or would you like to reference specific inherited members, like this? ::: path.to.my.Class.inherited_method |
sorry I did not had time to answer. The first one seems more natural to me. But both looks fine honestly |
Thanks! Yeah I've made it work in both cases anyway 🙂 |
Context
Hey, first thanks for the great tools!
I commented recently on this issue in pytkdocs.
My end goal is to make work the
inherited_members
of mkdocstring work.I was about to create a PR for pytkdocs but I saw that the new python handler of mkdostring is using griffe.
So I was wondering :
Thanks in advance
The text was updated successfully, but these errors were encountered: