How to use completion root without relative pathing
See original GitHub issueWhat is the problem?
Can’t seem to configure the new markdown.extension.completion.root
to what I expect. I want to set the path to match how the image will be served on the live site. Since I’m building this using Nuxt, the static
folder is automatically configured to serve any file in there. I don’t want my markdown files in the same folder because I use the Webpack Markdown loader to parse it and template the content before rendering HTML.
When I saw this new setting released I assumed it was to help with this situation. I also tried playing with the "markdown.extension.print.absoluteImgPath"
setting in conjunction with this but couldn’t get anything to change.
This is what the autocompletion looks like to me no matter what my settings:
How can I reproduce it?
In some project, create one folder that has markdown files and another static
folder that has images. Mine looks like this:
content/
guide/
index.md
static/
img/
my-pic.jpg
Set "markdown.extension.completion.root": "/static"
or "static"
, neither makes any difference.
In index.md
start creating an image ![](
, check the autocompletion path
Expected: /img/my-pic.jpg
Result: ../../static/img/my-pic.jpg
Is there any error message in the console?
No errors
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
I see it, that will clean up the results, thanks for adding that so quickly! It filters out relative results as soon as you type ‘/’.
It should be improved in the dev build.