You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a docstring includes HTML headers (<h1>, etc.) for example when I used an .. include:: some_file.html (or some markdown file which mixes markdown and HTML headers for some reason) directive, those headers are not included in the table of contents.
Proposal
markdown2 already supports this feature: trentm/python-markdown2#538.
All one would need to do, is set header-ids["mixed"] = True for the header-ids extra, which pdoc already uses.
Additional Context
Essentially, I would consider this the reverse of the markdown-in-html setting, which is already supported by pdoc. So I do not see a reason not to support this.
The text was updated successfully, but these errors were encountered:
Or should I add a new command-line argument, e.g. --mixed-header-ids which indicates this boolean value? One could leave its default to be False, therefore not changing the current behavior.
Problem Description
When a docstring includes HTML headers (
<h1>
, etc.) for example when I used an.. include:: some_file.html
(or some markdown file which mixes markdown and HTML headers for some reason) directive, those headers are not included in the table of contents.Proposal
markdown2 already supports this feature: trentm/python-markdown2#538.
All one would need to do, is set
header-ids["mixed"] = True
for the header-ids extra, which pdoc already uses.Additional Context
Essentially, I would consider this the reverse of the
markdown-in-html
setting, which is already supported by pdoc. So I do not see a reason not to support this.The text was updated successfully, but these errors were encountered: