fix vscode config for formatting markdown files now that we use two formatters for them

Author: DetachHead

.vscode/extensions.json

@@ -9,6 +9,7 @@
         "tamasfe.even-better-toml",
         "redhat.vscode-yaml",
         "github.vscode-github-actions",
-        "Orta.vscode-jest"
+        "Orta.vscode-jest",
+        "jota0222.multi-formatter"
     ]
 }

.vscode/settings.json

@@ -9,7 +9,7 @@
         "editor.codeActionsOnSave": {
             "source.fixAll.eslint": "always",
             "source.organizeImports": "always"
-        },
+        }
     },
     "[yaml]": {
         "editor.defaultFormatter": "esbenp.prettier-vscode",
@@ -19,12 +19,18 @@
         "editor.defaultFormatter": "tamasfe.even-better-toml",
         "editor.formatOnSave": true
     },
-    "[python][markdown]": {
+    "[python]": {
         "editor.defaultFormatter": "charliermarsh.ruff",
         "editor.codeActionsOnSave": {
             "source.organizeImports": "always"
         }
     },
+    "[markdown]": {
+        "editor.defaultFormatter": "Jota0222.multi-formatter",
+        // need prettier to format markdown and ruff to format python codeblocks inside the markdown files
+        "multiFormatter.formatterList": ["esbenp.prettier-vscode", "charliermarsh.ruff"],
+        "editor.formatOnSave": true
+    },
     "editor.codeActionsOnSave": {
         // this is the default, but we disable it explicitly to prevent any user settings from causing imports to get
         // sorted in typescript files since upstream has unsorted imports and we don't want to have to deal with
@@ -72,7 +78,7 @@
         "**/pyright-internal/src/tests/samples/*",
         "**/pyright-internal/typeshed-fallback/*",
         "**/docstubs/*",
-        "**/build/py_latest/upstream/*",
+        "**/build/py_latest/upstream/*"
     ],
     // even though python.terminal.activateEnvInCurrentTerminal is enabled, we still need to add the venv's script folder to the PATH
     // because vscode's npm tasks do not run with the activated venv