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
Copy file name to clipboardExpand all lines: docs/development/advanced/sandbox.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ If you prefer not use this approach, you can just compile and install the extens
9
9
10
10
## Start sandbox
11
11
12
-
These are configured in the `.vscode` directory of the repo.
12
+
These are configured in the `.vscode/launch.json` config.
13
13
14
14
Follow these steps:
15
15
@@ -25,7 +25,7 @@ Follow these steps:
25
25
- NB. You'll must run `npm run sb`**first** to ensure this directory exists and then run the debug action. Run that NPM command again whenever you want to clear the space and start over.
26
26
1. Click the run button.
27
27
28
-
That will start a new sandboxed VS Code session which has the extension built using the local code and _enabled_, and all other extensions _disabled_. At a lower level, it runs `npm compile` and `npm watch`.
28
+
That will start a new sandboxed VS Code session which has the extension built using the local code and _enabled_, and all other extensions _disabled_. At a lower level, it runs `npm compile` and `npm watch`. If you want to keep extensions enabled, remove the `--disable-extensions` flag in the launch config.
29
29
30
30
What is especially useful about this is that whenever an extension action is performed in the sandboxed VS Code window, if there are any logs for that then those will appear in the Debug Console of the _original_ VS Code window.
0 commit comments