-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Class methods' full source path is shown instead of the identifier used for it #111
Comments
Hmm, weird, I expose objects from submodules in my root init module too, and they correctly keep their alias path in the docs, for example: https://mkdocstrings.github.io/griffe/reference/griffe/#griffe.Attribute. I'll check out your repo again 🙂 |
Actually I'm able to replicate. It works fine when I let mkdocstrings unfold members of |
Great to hear! Let me know if there's anything you need from my side |
Previous accessing an alias member with the `[]` syntax would access the member on the target, instead of re-aliasing the member (to maintain alias path). Issue mkdocstrings-python#111: mkdocstrings/python#111
Pushed a fix, will release soon 🙂 |
Describe the bug
Hey! Thank you very much for the work on #90 and #91 :)
91 does seem fixed, but 90 doesn't. Upgraded
mkdocstrings-python
to1.5.3
andgriffe
to0.36.8
(see PR) and I'm still seeing the object's full path (temporian.implementation.numpy.data.event_set.EventSet.begin
) instead of the identifier I used for it (::: temporian.EventSet.begin
) in the header (see the rendered doc here). Note that I import theEventSet
class in my root__init__
which makes the identifier work.Full explanation in the original issue.
To Reproduce
See #90
Expected behavior
See #90
Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: