-
-
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
If class is aliased out of a module, explicitly listed members not rendered into documentation #100
Comments
I've found the issue -- in my documentation Seemingly, this is causing an issue for resolution for |
@pawamoy Btw, I swear this might be from a recent commit -- because I was successfully building and showing members from aliased (out of a module) names yesterday morning 😄 |
Hi @femtomc, thanks for the report! I'll investigate with what you gave me and come back to you if I need more info 🙂 |
Is this perhaps a recent change? https://mkdocstrings.github.io/griffe/reference/griffe/?h=public#griffe.Attribute.is_public My best guess as to what I missed. Edit: testing now. |
You're right, that highly possible. Just after our email exchange, I released mkdocstrings-python Insiders 1.5.1.1.3.0, you could try with that version, I think it will fix your issue. The explanation is: Griffe 0.35 returns members of aliases as aliases themselves. Previously the actual, resolved members were returned. This change was needed to preserve the path (the alias path, not the canonical one) of alias members. And an update was needed in mkdocstrings-python to support that. |
Okay will try! One moment, thanks! |
@pawamoy Should I set my inner (original) dataclasses Ah, I see -- so my dataclasses should automatically be public if I export them via |
If you refer to what is described in
...then no, by "object" here we refer to the Griffe object (Module/Class/Function/Attribute), not the actual object that is represented (your dataclass). The
Yes! If you declare |
I think either (a) something might still be wrong or (b) I'm misunderstanding how to document: Here, in In the markdown source:
Both are exported via an |
Thanks for the update. Is your repo public? Otherwise I'll run some tests with dummy code 👍 |
@pawamoy It is not public, but I could invite you if you want to do tests with it locally. I have to run now to do some errands, but let me know if that will help! Very easy for me to do. |
If that poses no issue to you or your peers/company, then sure, a temporary invitation is perfect 🙂 |
That's fine! If you want to interact with me about the repo, let's do so via an issue which you start at the repo itself :) thanks! |
This was a regression in the |
Describe the bug
Explicitly listing members, but their documentation is not being shown (and code which I'm executing using
markdown-exec
is not being shown).Expected behavior
Expect the members to show up in the documentation.
Screenshots
System (please complete the following information):
Additional context
Here's my
mkdocstrings
settings from mymkdocs.yml
:Here's a log when I serve the documentation:
The text was updated successfully, but these errors were encountered: