Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign updocument linking scheme; spawn more tickets #16
Comments
This comment has been minimized.
This comment has been minimized.
|
Link generation basically has two modes. The first mode is used when you ask for the static HTML docs of a Python module, and it sounds like that's what you're doing here. It has very limited support for linking. It basically only works for things inside the module that is being documented. The second mode is invoked only when you serve documentation from I'm going to change this ticket to "document linked; spawn more tickets" with the idea being that once I document the existing scheme in enough detail, it will be more clear what has to be done to improve the state of affairs. |
andy-maier commentedSep 27, 2014
Hi,
I am having trouble getting pdoc to create links to modules from within sub-modules of a package.
Example:
The pdoc documentation states that links need to be start with the package. In doing so, the link to 'foo.baz' in sub-module 'bar' is generated as a link in the version of sub-module 'bar' that is shown on the 'foo' page. However, on the 'foo.bar' page, the link to 'foo.baz' is formatted with monospace font, but is not generated as a link (marked as issue #1 in the code above).
Second, the link to the package 'foo' in sub-module 'foo.bar' is not generated as a link either (marked as issue #2 in the code above).
I have added some more variations, just to try them out.
Is there a documentation about the link generation by pdoc, and more generally, about which flavor of markdown it supports?
Regards,
Andy