Test updating markdown paths on file move/rename

[mjbvz]

Test for #148146

• Mac @rzhao271
• Linux @connor4312
• Windows @Yoyokrazy

Complexity: 4

Create Issue

---

Overview

This new feature allows markdown to automatically update all markdown links when a file is renamed/moved in the workspace. This is only supported for file moves/renames that happen within VS Code's explorer. It is also only supported for markdown style links (not html <a> links inside markdown)

Testing

• Enable this new behavior using "markdown.experimental.updateLinksOnFileMove.enabled": "prompt"

• Create some markdown links to local files:

  For this, try out some of these variants:

  • [text](/workspace/root/path/to/file.md)
  • [text](relative/path/to/file.md)
  • [text](path/fileNoExt) (should reference path/fileNoExt.md)
  • [text](path/file.md#some-header)
  • ![alt](path/img.png)
  • [definition]: /path/to/file.md

• Ensure that with prompt, renaming or moving any md or image file triggers a dialog that lets you update all markdown links

• Now try renaming some directories that contain the referenced files. Ensure this also triggers a update

• Finally try changing markdown.experimental.updateLinksOnFileMove.externalFileGlobs. This setting controls the types of files we try updating paths for (we always enable it for markdown files).

  The default value enables it for common image file names. Try enabling it for .js files or some other format too

[connor4312]

This doesn't work for me at all on Linux. Are there missing steps?

22-08-b08e21f5-8a38-4972-bab4-1699c6e8f942.mp4

[mjbvz]

Yes something is broken so please hold off on testing this

[mjbvz]

Should by fixed by #158965 but you'll need to be on tomorrow's insiders build to test

[Yoyokrazy]

Same user vs workspace setting issue as connor in #159084

Otherwise working as intended