Skip to content

docs: clarify links to mapped resources - #11199

Merged
vicancy merged 1 commit into
dotnet:mainfrom
zjdangge:codex/document-mapped-resource-links
Oct 22, 2026
Merged

vicancy merged 1 commit into
dotnet:mainfrom
zjdangge:codex/document-mapped-resource-links

Conversation

@zjdangge

Copy link
Copy Markdown
Contributor

Local links are resolved against source files even when a resource mapping copies them to another output directory. Add a worked example showing how ~/, src, and dest interact, including the InvalidFileLink warning caused by linking to the output path.

Relates to #11030.

Validation:

  • Built the current DocFX CLI for net10.0 in Release (0 warnings, 0 errors).
  • Reproduced the warning with the issue's destination-path link; source-root and relative source links both built without warnings and resolved to the copied image.
  • Built the exact documented JSON and Markdown example: 0 warnings, 0 errors; verified the generated image URL and output file.

@vicancy
vicancy merged commit 9bc2f5c into dotnet:main Oct 22, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants