-
-
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
Bases links aren't correct #5
Comments
I'm going to merge the above PR as it's better than what I have at the moment, but the problem is still there. |
Hello @samuelcolvin!
Hehehe glad you like mkdocstrings 😊 I think I know why bases use the canonical path rather than the public path (and I actually encountered this issue myself). |
OK it's an issue in mkdocstrings in fact, not Griffe, nor the Python handler 😄 |
Thanks so much for looking into this, please let me know via this issue when it's solved and i'll uprev dependencies. |
Could you try again with mkdocstrings 0.18.1? |
Thanks so much. See samuelcolvin/dirty-equals#21. Doesn't seem to work I'm afraid, see https://smokeshow.helpmanual.io/462a72276u0d3s2w4p1c/types/numeric/#dirty_equals.IsInt as an example. |
OK, I think it also needs mkdocstrings/autorefs#15 to work. |
Just released mkdocs-autorefs 0.4.0, should be fixed now 🙂 |
I seen to still be getting errors. I'm AFK but will look later. Or you can create a fresh PR to check. |
OK, this time it should be good 😫 🤞 |
great, thanks working. Thank you so much. |
Describe the bug
Thanks so much for mkdocstrings, I remembered this project from a conversation we had years ago. I'm now using it on a library I'm just writing docs for dirty-equals.
I've managed to set everything up the way I want it, except the "Bases" links are not working quite right.
This is because I have types declared in
dirty_equals._numeric
but recommended for import fromdirty_equals
. This is meaning that while heading ids are correct (e.g.dirty_equals.IsNumeric
), bases is generating a link of#dirty_equals._numeric.IsNumeric
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
docs requirements:
Any suggestions on a workaround or when a fix might be available would be wonderful.
The text was updated successfully, but these errors were encountered: