-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
"page not found" after using an internal hyperlink #615
Comments
I can't reproduce this. Could you please set up a git repo with a clean reproducer? |
Here's a git repo demonstrating the bug. I have |
Thanks for the excellent reproducer! Manually linking to submodules is unfortunately not supported right now. I've pushed #617 to make sure that the pdoc web server gives you a 404 right away. However, #544 should make it possible to do exactly what you are looking for: You can then use |
Ahh I see, thanks for that explanation! I will give that a try. |
Fixed as part of #544 and released in 14.1! :) |
Nice, thanks @mhils ! |
Problem Description
If using a hyperlink to something within the package, e.g.
[text to display](submodule1.submodule2.submodule3)
, after clicking on the hyperlink, all links on the linked page return a "page not found" error.Steps to reproduce the behavior:
submodule1
docstring we want to linkpackage.submodule1.submodule2.submodule3
, but we don't want to write the whole thing so we include a hyperlink:pdoc
, and click on the hyperlink.pdoc
correctly links this to the documentation forsubmodule3
.package/submodule1/submodule2/submodule3.html
) losesubmodule1/
. For example, the "up one level" button tries to link topackage/submodule2.html
, which doesn't exist so fails.System Information
The text was updated successfully, but these errors were encountered: