Describe the bug
I use ~ to set my image root, so I avoid "navigation" via ".." (folder up). Image-Tag or Include-Tag around the markdown files in different levels. So I like "~" to avoid folder-level issues.
I get a warning
About.md: warning InvalidFileLink: Invalid file link:(~/assets/img/views/en/light/About.png).
The images are "copied" in the build step from my "test-project" to assets/img/views, my docfx.json (partly)
{
"resource": [
...
{
"files": "**/*.png",
"src": "../App.Specs/screenshots/",
"dest": "assets/img/views",
"exclude": []
},
...
]
}
My Preferred way - can be used from everywhere
")
The "Classic way" with ".." navigation
")
To Reproduce
Steps to reproduce the behavior:
- Create a folder outside the docfx tree and add some images inside
- Copy the png-files in build step of docfx to "_site" target
- Create a markdown that reference the image with a ~-path
- Build the html _site via
dotnet docfx build
- BUG: AboutView.md: warning InvalidFileLink: Invalid file link:(~/assets/img/views/en/light/About.png).
Expected behavior
The ~ should be a valid link, No InvalidFileLink warning in build
Context (please complete the following information):
- OS: Windows
- Docfx version: [e.g. 2.78.3]
Additional context
nothing
Describe the bug
I use
~to set my image root, so I avoid "navigation" via ".." (folder up). Image-Tag or Include-Tag around the markdown files in different levels. So I like "~" to avoid folder-level issues.I get a warning
The images are "copied" in the build step from my "test-project" to
assets/img/views, my docfx.json (partly){ "resource": [ ... { "files": "**/*.png", "src": "../App.Specs/screenshots/", "dest": "assets/img/views", "exclude": [] }, ... ] }My Preferred way - can be used from everywhere
The "Classic way" with ".." navigation
To Reproduce
Steps to reproduce the behavior:
dotnet docfx buildExpected behavior
The ~ should be a valid link, No
InvalidFileLinkwarning in buildContext (please complete the following information):
Additional context
nothing