You can probably change those to emit Markdown instead and then add a | to_html filter in the HTML template. # Check if the object we are interested is also imported and re-exposed in the current namespace.

'''Create a link for a specific `(modulename, qualname)` tuple.''' Module, qualname = split_identifier( context, identifier) Module = contextįor qualname in qualname_candidates( identifier, namespace): # Check if this is a local reference within this module? Identifiers referencing unknown modules or modules thatĪre not rendered at the moment will be ignored.Ī piece of text is considered to be an identifier if it either contains a `.` or is surrounded by `` tags. If you are interested in building out Jinja2 templates for Markdown output I can rebase the markdown branch onto main, let me know what you think! pass_contextĭef linkify( context: Context, code: str, namespace: str = '') -> str: Whatsoever, I agree that a direct Markdown export would work better here. Not sure if you have seen, there are a few mkdocs-specific comments in the README. Integrating with mkdocs is definitely a bit quirky at the moment. I think proper markdown output support would make this challenge at least a tiny bit easier since the jinja templates should be simpler to modify to fit any weird mkdocs→pdoc linking issues. I'm also struggling with links not working because of differences in how mkdocs treats files as directories in the URL but pdoc links to html files (that do not exist). I am using mkdocs but, for example, the search feature of mkdocs will pick up on the html and show a lot of nonsense in the results because of it. There's quite a bit wrong with simply renaming html files to md files right now. Hey any chance we can create a ticket for the markdown output support? I saw there is one that was closed but the markdown branch is over a hundred commits behind and I would love to track it properly :)

Macdown export