You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm using FrontMatter to manage my blog built on static site generator Hugo. As per default Hugo configuration content markdown files located in <BLOG_ROOT>/content/posts. This directory is registered in Settings > Content folders and FM plugin sees them as posts.
For internal linking of posts I use following notation: [link to another post](/another-post). Once site is generated URI of the link is prefixed with baseURL configured in Hugo config.toml and full URL becomes <baseURL>/another-post (e.g. https://mynextbestrace.com/another-post). So far so good.
In editing mode, however, when I want to navigate to the linked post I'm getting a popup dialog saying that the linked file doesn't exist. This is because VSCode is looking for the file <BLOG_ROOT>/another-post.md, and not <BLOG_ROOT>/content/posts/another-post.md.
Describe the solution you'd like
In order to support navigation through internal links in editing mode we need to have a resolver which would "translate" internal link URI to the proper file name.
We could have a setting: internalLinkedFilePrefix = 'content/posts'.
Whenever we try to navigate the local link [link to another post](/another-post) plugin will "resolve" it to a proper file name by adding a value of internalLinkedFilePrefix as a prefix and will open the file content/posts/another-post.md.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm using FrontMatter to manage my blog built on static site generator Hugo. As per default Hugo configuration content markdown files located in <BLOG_ROOT>/content/posts. This directory is registered in Settings > Content folders and FM plugin sees them as posts.
For internal linking of posts I use following notation:
[link to another post](/another-post)
. Once site is generated URI of the link is prefixed withbaseURL
configured in Hugo config.toml and full URL becomes<baseURL>/another-post
(e.g. https://mynextbestrace.com/another-post). So far so good.In editing mode, however, when I want to navigate to the linked post I'm getting a popup dialog saying that the linked file doesn't exist. This is because VSCode is looking for the file <BLOG_ROOT>/another-post.md, and not <BLOG_ROOT>/content/posts/another-post.md.
Describe the solution you'd like
In order to support navigation through internal links in editing mode we need to have a resolver which would "translate" internal link URI to the proper file name.
We could have a setting: internalLinkedFilePrefix = 'content/posts'.
Whenever we try to navigate the local link
[link to another post](/another-post)
plugin will "resolve" it to a proper file name by adding a value of internalLinkedFilePrefix as a prefix and will open the file content/posts/another-post.md.The text was updated successfully, but these errors were encountered: