Skip to content

Commit 3771d3b

Browse files
committed
docs: add notes to sandbox.md
1 parent 4570b30 commit 3771d3b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/development/advanced/sandbox.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ If you prefer not use this approach, you can just compile and install the extens
99

1010
## Start sandbox
1111

12-
These are configured in the `.vscode` directory of the repo.
12+
These are configured in the `.vscode/launch.json` config.
1313

1414
Follow these steps:
1515

@@ -25,7 +25,7 @@ Follow these steps:
2525
- 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.
2626
1. Click the run button.
2727

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.
2929

3030
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.
3131

0 commit comments

Comments
 (0)