[typedoc-plugin-markdown@next] Bug: Links to README.md
in header broken in member pages.
#483
Labels
next
Fix available in the '@next' release
Hello,
I have an issue where the links to the module
README.md
files are not relative from the member pages when building a doc for a monorepository ("entryPointStrategy": "packages"
, based on Gerrit0 example).Version:
4.0.0-next.23(typedoc@0.25.1)
I am using the default
outputFileStrategy
(members
).For example, taking the tree shown in the option guide.
In the page
ClassA.md
, the header would uses[README](README.md) ∙ [API](../modules.md)
for the links, correctly using the relative for themodules.md
page, but not for theREADME.md
page.It is to note that the breadcrumbs do get relative links as expected, but they all point to the modules files, which already get its relative links correctly in the header.
[API](../../../modules.md) > [package-1](../modules.md) > Content
I was looking at the tests, and I'm not sure if I am reading this right, but it looks that this case is not covered. Seems that
README.md
themselves are checked.https://github.com/tgreyuk/typedoc-plugin-markdown/blob/3a0a5bea81b14857d387fbfba599200212634eeb/packages/typedoc-plugin-markdown/test/specs/__snapshots__/readmes.spec.ts.snap#L20-L48
modules.md
links, not the readme (under bothpackage-1
andpackage-2
, the URL is only for themodules.md
and there is noREADME.md
URLs.https://github.com/tgreyuk/typedoc-plugin-markdown/blob/3a0a5bea81b14857d387fbfba599200212634eeb/packages/typedoc-plugin-markdown/test/specs/__snapshots__/navigation.spec.ts.snap#L3-L44
https://github.com/tgreyuk/typedoc-plugin-markdown/blob/3a0a5bea81b14857d387fbfba599200212634eeb/packages/typedoc-plugin-markdown/test/specs/__snapshots__/groups.spec.ts.snap#L493-L509
README.md
files are detected.https://github.com/tgreyuk/typedoc-plugin-markdown/blob/3a0a5bea81b14857d387fbfba599200212634eeb/packages/typedoc-plugin-markdown/test/specs/__snapshots__/urls.spec.ts.snap#L113-L124
packages
entry point strategy; but they do get relative URL to theREADME.md
files.The text was updated successfully, but these errors were encountered: