When working with "markdown.preferredMdPathExtensionStyle": "removeExtension" set, and a mix of MDX and MD files, it is not possible to validate and autocomplete links to MDX files from MD files using this language service.
The root cause, at least for validation, seems to be
|
export function tryAppendMarkdownFileExtension(config: LsConfiguration, linkUri: URI): URI | undefined { |
This function requires all extensionless links in MD files to be handled by the language service. However, MDX files can't be handled by this service.
Perhaps a new setting ("markdown.knownMdExtensions": ["md", "mdx"]) could be added to allow link validation to find the file?
When working with
"markdown.preferredMdPathExtensionStyle": "removeExtension"set, and a mix of MDX and MD files, it is not possible to validate and autocomplete links to MDX files from MD files using this language service.The root cause, at least for validation, seems to be
vscode-markdown-languageservice/src/workspace.ts
Line 227 in 7156aba
This function requires all extensionless links in MD files to be handled by the language service. However, MDX files can't be handled by this service.
Perhaps a new setting (
"markdown.knownMdExtensions": ["md", "mdx"]) could be added to allow link validation to find the file?