Repository navigation
Conversation
|
@Goldloli is attempting to deploy a commit to the Docsify Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for your feedback. There are other documents that use this format as well. Could you update them as well? |
|
Good point — I extended the change to every remaining docs page that links to a sibling page without the
Together with the first three files, the branch now fixes 8 files / 18 links. I checked every target resolves to an existing One exception: |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The docs pages for Prism highlighting and plugins link to sibling pages without the
.mdextension:docs/language-highlight.md:themesandthemes#theme-propertiesdocs/emoji.md:configuration#nativeemojidocs/write-a-plugin.md:configuration#catchpluginerrorsThose spellings work on the rendered docsify site (its router resolves extension-less paths), but on GitHub the same links resolve relative to the markdown file and point at non-existent
docs/themes/docs/configurationpaths, so they 404 when reading the docs in the repository (and in any renderer that treats them as plain relative links).This adds the
.mdextension, which GitHub resolves correctly and docsify also handles (the docs already contain links likeconfiguration.md?id=...). The anchor ids (theme-properties,nativeemoji,catchpluginerrors) already exist in the target pages.Verification: checked the three target pages exist (
docs/themes.md,docs/configuration.md) and the anchors are present in them; only documentation links are touched, no code or test changes.npm testwas not run because the change is limited todocs/markdown and does not affect the test suite; happy to run it if you want a green run on the PR anyway.