I noticed a few quirks with the VSCode JSON files generated in the .vscode directory using the build build -m ::vscode command as described here.
(1) Using these JSON scripts, VSCode reports a deprecated entry:
WAS: "runToMain": true
IS: "runToEntryPoint": "main"
(2) The script generating these JSON files is generating them as JSONC (JSON with comments). Looks like VSCode doesn't have any problem reading it, but my editor NEOVIM was a sea of bright red denoting the JSON "errors"
(3) Documentation search oddness... if you search for VSCODE, there are two results. But if you search for "VISUAL STUDIO CODE", only one result (the page about using VSCode along with WSL2 is missing).
VSCode isn't something I'll use very often, but the debugger integration is very good. Much better than I expected.
I noticed a few quirks with the VSCode JSON files generated in the
.vscodedirectory using thebuild build -m ::vscodecommand as described here.(1) Using these JSON scripts, VSCode reports a deprecated entry:
(2) The script generating these JSON files is generating them as JSONC (JSON with comments). Looks like VSCode doesn't have any problem reading it, but my editor NEOVIM was a sea of bright red denoting the JSON "errors"
(3) Documentation search oddness... if you search for VSCODE, there are two results. But if you search for "VISUAL STUDIO CODE", only one result (the page about using VSCode along with WSL2 is missing).
VSCode isn't something I'll use very often, but the debugger integration is very good. Much better than I expected.