Replies: 2 comments
-
|
Hello! No there's no timeline. I'm currently getting back to open source after a (subjectively) long burnout. I'm not in capacity to build up a timeline yet. I agree that supporting inherited members is an important feature. It's definitely on the "to do" list. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Now supported 🙂 https://mkdocstrings.github.io/python/usage/configuration/members/#inherited_members |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the migration notes for 0.19, I see the note:
As far as I can tell, neither the new experimental
pythonhandler, nor the oldpython-legacysupport this option right now. Am I missing something?If it's the case that
inherited_membersis a casualty of handler changes, is there a timeline for when to expect inherited members? As someone using mkdocstrings before the recent handler changes and configuration interface changes, it feels like a significant regression to not have this functionality at all.This is important functionality that I need for my documentation, as I have abstract base classes that implement the bulk of the API interface, but the concrete classes are what users actually use and will look up documentation for.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions