Skip to content

Commit ec31234

Browse files
authored
Document VS Code extension and expand test coverage (#409)
* Document VS Code extension and expand test coverage Add a /vscode-extension/ docs section (overview, installation with dynamic VSIX download link, configuration, features) parallel to the MCP Server section. Replace the placeholder activation test with a real Extension Host integration suite, fix the rootDir trap so unit tests can import production code directly, and add unit tests for WebDavMappingsProvider and SandboxConfigProvider. Extend ci-vs-extension.yml to also run on SDK changes and cache the .vscode-test binary. * Doc fixes and review nits - Drop unimplemented "Compare with Instance" diff from features.md and remove its placeholder image; the diffCartridge command is stub functionality. - Fix project-root pinning docs: "Use as B2C Commerce Root" only shows on a workspace-root folder when the workspace has more than one folder open; "Reset" is palette-only. - Replace internal-source pointer with an inline rule in the cloned sandbox indicators paragraph. - Add 24h TTL to the VSIX release data loader cache so a maintainer who cuts a release won't see a stale version on the next local docs build. - Include pnpm-lock.yaml in the .vscode-test cache key so a test-cli / test-electron version bump invalidates the cache. - Comment the activation test's command-registration check to explain why it doubles as a swallowed-failure detector. - Tidy webdav-mappings.test.ts stub. * Add VS Code to homepage hero pills; shorten MCP Server to MCP * Visible SVG screenshot placeholders Replace the invisible 1x1 PNG placeholders with per-slot SVG placeholders that render as dashed-border boxes with the slot title, description, and a "replace with <slot>.png" hint. Reviewers and the user can now see exactly where each screenshot belongs on the rendered page. Updated TODO comments to spell out the swap path (.svg -> .png) and added images/README.md with the replacement workflow. * Move VS Code Extension above MCP Server in sidebar and nav * Add VS Code Extension install quick-start to homepage * Add extension telemetry; restructure configuration & features docs Telemetry: - Wire SDK Telemetry into the VS Code extension (project=b2c-vs-extension) using the same App Insights connection string as the MCP server. - Lifecycle events (EXTENSION_ACTIVATED / DEACTIVATED / ACTIVATION_FAILED) plus per-command COMMAND_INVOKED with outcome and duration via registerSafeCommand. Exceptions reported through sendException. - Honors vscode.env.isTelemetryEnabled (telemetry.telemetryLevel) plus SFCC_DISABLE_TELEMETRY / SF_DISABLE_TELEMETRY. Persists anonymous cliId in globalStorageUri. Docs: - Lead Configuration with "Connecting to a B2C Instance" — a per-feature credential requirements table modeled on the CLI's per-command auth sections (sandbox.md, scapi-schemas.md). Adds an example dw.json with inline comments tagging each block to features. - Demote b2c-dx.* settings to a "Settings reference" section near the bottom with a clear "you usually don't need to change these" callout. - Add Telemetry section documenting what's collected, what's not, and three independent opt-out paths. - Add per-feature "Requires" callouts on every feature in features.md plus a top-of-page jump nav. * Telemetry: non-blocking, broader categories, simple opt-out setting - initTelemetry is now fire-and-forget — client.start() runs in the background so activation never blocks on it. trackEvent() was already in-memory + batched, so subsequent sendEvent calls are non-blocking. - Drop per-command COMMAND_INVOKED events. Replace with FEATURE_USED, bucketed by broad category (sandbox/webdav/content/codeSync/apiBrowser/ debugger/scaffold/cap/pageDesigner/logs/instance) and deduped to one event per category per session. - Add b2c-dx.telemetry.enabled setting (default true). Telemetry is off if any of the three signals say off: VS Code's telemetry.telemetryLevel, this setting, or the SF/SFCC env var. - Strip the Telemetry section from the docs site — the setting's description in the VS Code Settings UI is the disclosure surface. Add the row to the configuration page's settings reference table. - Wire markFeatureUsed into the page-designer command and the script debugger factory so non-safety-wrapped features still register usage. * Add real overview screenshot * Friendlier docs voice; restructure highlights; add real screenshots - Soften the intro and per-feature copy on index.md / installation.md; remove dw.json/SFCC_* jargon from outward-facing prose. - Reorder highlights and add screenshots for the three biggest ones (Sandbox Realm Explorer, Library Explorer, Script Debugger). Make highlight images clickable so the inline thumbnail can be expanded to the full-resolution capture. - Rename Cartridge Code Sync -> "Cartridge Management and Code Watch/ Upload"; add SCAPI API Explorer as a dedicated highlight. - Drop the Page Designer Assistant highlight; promote Scaffolding to a highlight in its place (covers cartridges, controllers, hooks, jobs). - Expand the Script Debugger blurb to call out controllers, jobs, custom scripts, SCAPI hooks, Custom APIs, breakpoints, and log points. - Delete features.md; fold Log Tailing, Active Instance Status Bar, and B2C CLI Plugin Support onto index.md and update sidebar / cross-links. - Drop Project Root Pinning from configuration.md (uncommon use case). - Mention the VS Code Extension on docs/guide/index.md with a quick- install block parallel to the CLI/MCP installs, using the existing release.data.ts loader.
1 parent 7b3524f commit ec31234

52 files changed

Lines changed: 1506 additions & 136 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
'@salesforce/b2c-dx-docs': patch
3+
---
4+
5+
Document the B2C DX VS Code Extension. New `/vscode-extension/` section with overview, installation (with a dynamic download link to the latest VSIX release), configuration reference, and a feature tour covering Sandbox Realm Explorer, Cartridge Code Sync, WebDAV Browser, Content Libraries, SCAPI API Browser, B2C Script Debugger, scaffold/CAP install, log tailing, and B2C CLI plugin support.

.changeset/vscode-telemetry.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
'b2c-vs-extension': minor
3+
---
4+
5+
Add anonymous usage telemetry (extension activation/deactivation lifecycle, broad feature-category usage, exceptions) to help prioritize fixes during the Developer Preview. Sending is non-blocking. Honors the new `b2c-dx.telemetry.enabled` setting (default `true`), VS Code's `telemetry.telemetryLevel`, and the `SFCC_DISABLE_TELEMETRY` / `SF_DISABLE_TELEMETRY` environment variables. No credentials, hostnames, or business data are collected.

.github/workflows/ci-vs-extension.yml

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,19 @@ on:
66
- main
77
paths:
88
- 'packages/b2c-vs-extension/**'
9+
- 'packages/b2c-tooling-sdk/**'
10+
- 'pnpm-lock.yaml'
11+
- 'pnpm-workspace.yaml'
12+
- '.github/workflows/ci-vs-extension.yml'
913
pull_request:
1014
branches:
1115
- main
1216
paths:
1317
- 'packages/b2c-vs-extension/**'
18+
- 'packages/b2c-tooling-sdk/**'
19+
- 'pnpm-lock.yaml'
20+
- 'pnpm-workspace.yaml'
21+
- '.github/workflows/ci-vs-extension.yml'
1422

1523
permissions:
1624
contents: read
@@ -51,6 +59,14 @@ jobs:
5159
restore-keys: |
5260
${{ runner.os }}-pnpm-store-
5361
62+
- name: Cache VS Code test binary
63+
uses: actions/cache@v5
64+
with:
65+
path: packages/b2c-vs-extension/.vscode-test
66+
key: ${{ runner.os }}-vscode-test-${{ hashFiles('packages/b2c-vs-extension/.vscode-test.mjs', 'pnpm-lock.yaml') }}
67+
restore-keys: |
68+
${{ runner.os }}-vscode-test-
69+
5470
- name: Install dependencies
5571
run: pnpm install --frozen-lockfile
5672

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ docs/.vitepress/cache
2727
docs/api/
2828

2929
*dw.json*
30+
!packages/b2c-vs-extension/src/test/fixtures/**/dw.json
3031
.env
3132
.config/wt.toml
3233
.b2c/

docs/.vitepress/config.mts

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,14 @@ const guidesSidebar = [
7676
{text: 'Commerce Apps (CAPs)', link: '/guide/commerce-apps'},
7777
],
7878
},
79+
{
80+
text: 'VS Code Extension',
81+
items: [
82+
{text: 'Overview', link: '/vscode-extension/'},
83+
{text: 'Installation', link: '/vscode-extension/installation'},
84+
{text: 'Configuration', link: '/vscode-extension/configuration'},
85+
],
86+
},
7987
{
8088
text: 'MCP Server',
8189
items: [
@@ -197,7 +205,7 @@ document.addEventListener('click', (e) => {
197205

198206
export default defineConfig({
199207
title: 'B2C Developer Toolkit',
200-
description: 'Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, SDK, and IDE extensions for Salesforce B2C Commerce',
208+
description: 'Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, SDK, and the B2C DX VS Code Extension for Salesforce B2C Commerce',
201209
base: basePath,
202210

203211
head: [['script', {}, versionSwitchScript]],
@@ -263,6 +271,7 @@ export default defineConfig({
263271
nav: [
264272
{text: 'Guides', link: '/guide/'},
265273
{text: 'Skills', link: '/guide/agent-skills'},
274+
{text: 'VS Code', link: '/vscode-extension/'},
266275
{text: 'MCP', link: '/mcp/'},
267276
{text: 'Reference', link: '/cli/'},
268277
{text: 'SDK', link: '/api/'},
@@ -280,6 +289,7 @@ export default defineConfig({
280289
sidebar: {
281290
'/mcp/tools/': referenceSidebar,
282291
'/mcp/': guidesSidebar,
292+
'/vscode-extension/': guidesSidebar,
283293
'/cli/': referenceSidebar,
284294
'/guide/': guidesSidebar,
285295
'/api/': [

docs/guide/ide-integration.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,9 @@ description: Configure IDE tooling like Prophet VS Code extension and IntelliJ S
44

55
# IDE Integration
66

7-
This guide explains how to connect IDE extensions to your B2C CLI configuration.
7+
This guide explains how to connect third-party IDE extensions (Prophet, IntelliJ SFCC) to your B2C CLI configuration.
8+
9+
> Looking for the **Salesforce-published B2C DX VS Code Extension**? See the dedicated [VS Code Extension](../vscode-extension/) section — it consumes `dw.json` and the active instance directly, no bridge script required.
810
911
## Prophet VS Code Extension
1012

docs/guide/index.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,19 @@
11
---
2-
description: Introduction to the Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, and SDK for Salesforce Agentforce Commerce.
2+
description: Introduction to the Agentic B2C Developer Toolkit — CLI, Agent Skills, MCP Server, VS Code extension, and SDK for Salesforce Agentforce Commerce.
33
---
44

5+
<script setup>
6+
import {data as vsxRelease} from '../vscode-extension/release.data.ts';
7+
</script>
8+
59
# Introduction
610

711
The Agentic B2C Developer Toolkit exposes the B2C Commerce platform as commands, MCP tools, and coding skills — so you and your AI agents can build, deploy, and operate storefronts from the terminal or directly inside your IDE. No clicking through Business Manager to deploy, no context-switching to run a job, no manual copy-paste when your agent needs to touch a live sandbox.
812

913
- **B2C CLI** — a single command for every workflow: cartridge deploys, jobs, ODS/MRT, WebDAV, site archives, SLAS, eCDN, Account Manager, CI/CD.
1014
- **Agent Skills** — 30+ preconfigured skills that teach your coding agent (Claude Code, Cursor, Agentforce Vibes, Copilot, Codex) how B2C Commerce works — SCAPI Custom APIs, SLAS, SFRA controllers and forms, ISML, Page Designer, hooks, custom objects — and which CLI commands to run when.
1115
- **MCP Server** — a focused set of MCP tools that complement the CLI for agent-driven workflows.
16+
- **VS Code Extension** *(Developer Preview)* — sandbox management, cartridge code sync, content libraries, SCAPI explorer, and a server-side script debugger right inside VS Code.
1217
- **Tooling SDK** — everything the CLI does, available as a typed TypeScript SDK for custom integrations.
1318

1419
## Quick CLI Install
@@ -74,13 +79,37 @@ claude plugin install b2c-dx-mcp --scope project
7479

7580
See the [MCP Server Installation Guide](/mcp/installation) for full setup steps and troubleshooting.
7681

82+
## Quick VS Code Extension Install <Badge type="warning" text="Developer Preview" />
83+
84+
The B2C DX VS Code Extension brings sandbox management, code sync, content libraries, the SCAPI explorer, and a server-side debugger into VS Code. It isn't on the Marketplace yet — install the latest pre-built `.vsix` from GitHub.
85+
86+
<div v-if="!vsxRelease.unavailable">
87+
88+
Latest version: <strong>{{ vsxRelease.version }}</strong> · <a :href="vsxRelease.vsixDownloadUrl">Download {{ vsxRelease.vsixAssetName }}</a> · <a :href="vsxRelease.releasePageUrl">Release notes</a>
89+
90+
```bash
91+
code --install-extension {{ vsxRelease.vsixAssetName }}
92+
# or, in Cursor:
93+
cursor --install-extension {{ vsxRelease.vsixAssetName }}
94+
```
95+
96+
</div>
97+
<div v-else>
98+
99+
The extension hasn't shipped a release yet. Browse the <a :href="vsxRelease.fallbackUrl">GitHub releases page</a> for `b2c-vs-extension@*` tags.
100+
101+
</div>
102+
103+
See the [VS Code Extension](/vscode-extension/) section for the full overview, [installation](/vscode-extension/installation), and [configuration](/vscode-extension/configuration).
104+
77105
## Next Steps
78106

79107
- [Authentication Setup](./authentication) - Set up Account Manager, OCAPI, and WebDAV
80108
- [Analytics Reports (CIP/CCAC)](./analytics-reports-cip-ccac) - Run curated analytics reports and SQL queries
81109
- [Configuration](./configuration) - Configure instances and credentials
82110
- [IDE Integration](./ide-integration) - Connect Prophet VS Code to B2C CLI configuration
83111
- [MCP Server](/mcp/) - AI-assisted development with Model Context Protocol
112+
- [VS Code Extension](/vscode-extension/) - Sandbox management, code sync, and the script debugger inside VS Code
84113
- [CLI Reference](/cli/) - Browse available commands
85114
- [MCP Tools](/mcp/toolsets) - Explore MCP tools for cartridges, MRT, SCAPI, and so on
86115
- [SDK Reference](/api/) - Explore the SDK

docs/index.md

Lines changed: 42 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ renameNotice:
1010
hero:
1111
name: Agentic B2C Developer Toolkit
1212
text: ""
13-
tagline: CLI, Agent Skills, MCP Server, and IDE extensions for Salesforce Agentforce Commerce — everything you and your coding agent need to build, deploy, and operate B2C Commerce together.
13+
tagline: CLI, Agent Skills, MCP Server, and the B2C DX VS Code Extension for Salesforce Agentforce Commerce — everything you and your coding agent need to build, deploy, and operate B2C Commerce together.
1414
image:
1515
src: /hero-collage.png
1616
alt: Agentic B2C Developer Toolkit — CLI, Agentforce Vibes, and Claude Code
@@ -22,11 +22,11 @@ hero:
2222
text: Agent Skills
2323
link: /guide/agent-skills
2424
- theme: alt
25-
text: MCP Server
26-
link: /mcp/
25+
text: VS Code
26+
link: /vscode-extension/
2727
- theme: alt
28-
text: Reference
29-
link: /cli/
28+
text: MCP
29+
link: /mcp/
3030

3131
features:
3232
- icon:
@@ -53,8 +53,20 @@ features:
5353
details: A focused set of MCP tools that complement the CLI for agent-driven workflows. Pairs naturally with skills.
5454
link: /mcp/
5555
linkText: MCP Server
56+
- icon:
57+
src: /icons/cli.svg
58+
width: 48
59+
height: 48
60+
title: VS Code Extension (Developer Preview)
61+
details: B2C DX activity-bar containers for sandbox lifecycle, cartridge code sync, WebDAV, content libraries, SCAPI, and a B2C script debugger — all driven by the same dw.json the CLI uses.
62+
link: /vscode-extension/
63+
linkText: VS Code Extension
5664
---
5765

66+
<script setup>
67+
import {data as vsxRelease} from './vscode-extension/release.data.ts';
68+
</script>
69+
5870
## Install the CLI
5971

6072
::: code-group
@@ -117,3 +129,28 @@ npx @salesforce/b2c-cli setup skills
117129

118130
:::
119131

132+
## Install the VS Code Extension <Badge type="warning" text="Developer Preview" />
133+
134+
The extension is not yet published to the VS Code Marketplace — install the latest pre-built `.vsix` from GitHub releases.
135+
136+
<div v-if="!vsxRelease.unavailable" class="b2c-vsx-install">
137+
<p>
138+
Latest release: <strong>{{ vsxRelease.version }}</strong>
139+
<span> · </span>
140+
<a :href="vsxRelease.vsixDownloadUrl">Download {{ vsxRelease.vsixAssetName }}</a>
141+
<span> · </span>
142+
<a :href="vsxRelease.releasePageUrl">Release notes</a>
143+
</p>
144+
<p>Then install with:</p>
145+
<pre><code>code --install-extension {{ vsxRelease.vsixAssetName }}
146+
# or, in Cursor:
147+
cursor --install-extension {{ vsxRelease.vsixAssetName }}</code></pre>
148+
</div>
149+
<div v-else>
150+
151+
Browse the [GitHub releases page]({{ vsxRelease.fallbackUrl }}) for `b2c-vs-extension@*` tags and install the `.vsix` via `code --install-extension <file>.vsix`.
152+
153+
</div>
154+
155+
Detailed setup: [Installation](/vscode-extension/installation) · [Configuration](/vscode-extension/configuration)
156+
Lines changed: 120 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,120 @@
1+
---
2+
description: Connect the B2C DX VS Code Extension to a B2C Commerce instance — credentials, OAuth, telemetry, and the b2c-dx.* settings reference.
3+
---
4+
5+
# Configuration
6+
7+
The extension reuses the [B2C CLI](../guide/configuration)'s configuration system, so anything that works with `b2c` works here — `dw.json`, `SFCC_*` environment variables, and active-instance selection.
8+
9+
This page covers:
10+
11+
- [Connecting to a B2C Instance](#connecting-to-a-b2c-instance) — credentials per feature.
12+
- [Switching the Active Instance](#switching-the-active-instance) — single-workspace, multi-instance.
13+
- [Settings Reference](#settings-reference) — the `b2c-dx.*` toggles and verbosity controls.
14+
15+
## Connecting to a B2C Instance
16+
17+
The extension needs different credentials depending on which feature you use. **A `dw.json` at your workspace root is the recommended setup** — populate the fields each feature needs, and the extension picks them up automatically.
18+
19+
### Per-feature requirements
20+
21+
A summary by feature:
22+
23+
| Feature | Required `dw.json` fields |
24+
| ------- | ------------------------- |
25+
| **Sandbox Realm Explorer** | OAuth (browser login by default; `client-id` + `client-secret` for headless). `Sandbox API User` role with a tenant filter. |
26+
| **WebDAV Browser** | `hostname`, `username`, `password` (WebDAV access key). OAuth (`client-id` + `client-secret`) also accepted. |
27+
| **Content Libraries** | Same as WebDAV. Optionally `contentLibrary` (or `libraries`) to seed the tree. |
28+
| **Cartridge Code Sync** | WebDAV for transfer **and** OCAPI (`client-id` + `client-secret`) for code-version operations. |
29+
| **SCAPI API Browser** | `client-id`, `client-secret`, `short-code`, `tenant-id`. |
30+
| **B2C Script Debugger** | WebDAV (for source-mapping). |
31+
| **Log Tailing** | WebDAV (logs are read from `Logs/`). |
32+
| **CAP install** | WebDAV; some apps additionally require OAuth client credentials. |
33+
| **Scaffold**, **Page Designer Assistant** | None — local-only. |
34+
35+
### Example `dw.json`
36+
37+
```jsonc
38+
{
39+
// WebDAV (Code Sync, WebDAV Browser, Content Libraries, Log Tailing, Debugger)
40+
"hostname": "abcd-001.dx.commercecloud.salesforce.com",
41+
"username": "your-bm-username",
42+
"password": "your-webdav-access-key",
43+
"code-version": "version1",
44+
45+
// OCAPI / OAuth (Sandbox API, Code Versions, CAP)
46+
"client-id": "...",
47+
"client-secret": "...",
48+
49+
// SCAPI (API Browser)
50+
"short-code": "...",
51+
"tenant-id": "...",
52+
53+
// Optional — content tree seed
54+
"contentLibrary": "your-library-id"
55+
}
56+
```
57+
58+
You can also set any of these via `SFCC_*` environment variables (`SFCC_SERVER`, `SFCC_USERNAME`, `SFCC_CLIENT_ID`, `SFCC_TENANT_ID`, etc.). See the [CLI Configuration guide](../guide/configuration) for the complete list and precedence rules, and the [Authentication Setup guide](../guide/authentication) for OAuth scope requirements and Account Manager API client setup.
59+
60+
<!-- TODO(screenshot): replace ./images/settings.svg with ./images/settings.png — Settings UI filtered to b2c-dx -->
61+
62+
## Switching the Active Instance
63+
64+
When `dw.json` defines multiple named instances (the recommended pattern for working across dev / staging / sandbox), click the cloud icon in the status bar to run **B2C DX: Switch Active Instance** — a quick-pick over the configured instances. Selecting a new one updates the underlying `dw.json` active-instance pointer and refreshes every view.
65+
66+
The same pointer is shared with the CLI: switching here is equivalent to running `b2c setup instance set-active <name>`.
67+
68+
## Settings Reference
69+
70+
These VS Code settings live under the `b2c-dx.*` namespace. **You usually don't need to change any of them** — they exist for niche cases like disabling a feature you don't use, or quieting the log channel for a bug report. To browse: **Settings** (Cmd+,) → search for `b2c-dx`.
71+
72+
### Feature toggles
73+
74+
Each feature is enabled by default. Set to `false` to skip its activation entirely (no tree views, no commands, no context-menu entries). Useful for trimming the UI, isolating activation issues, or running in a project where a feature isn't applicable.
75+
76+
| Setting | Default |
77+
| ------- | ------- |
78+
| `b2c-dx.features.sandboxExplorer` | `true` |
79+
| `b2c-dx.features.webdavBrowser` | `true` |
80+
| `b2c-dx.features.contentLibraries` | `true` |
81+
| `b2c-dx.features.codeSync` | `true` |
82+
| `b2c-dx.features.logTailing` | `true` |
83+
| `b2c-dx.features.scaffold` | `true` |
84+
| `b2c-dx.features.apiBrowser` | `true` |
85+
| `b2c-dx.features.cap` | `true` |
86+
87+
The B2C Script Debugger registers regardless of these toggles — it activates only when a `b2c-script` launch configuration is used.
88+
89+
### Verbosity, polling, telemetry
90+
91+
| Setting | Default | Description |
92+
| ------- | ------- | ----------- |
93+
| `b2c-dx.logLevel` | `info` | Verbosity for the **B2C DX** output channel. Allowed: `trace`, `debug`, `info`, `warn`, `error`, `silent`. Applied immediately on change. Drop to `debug` or `trace` when filing a bug. |
94+
| `b2c-dx.sandbox.pollingInterval` | `10` | Seconds between polls while a sandbox is in a transitional state (`creating`, `starting`, `stopping`, `deleting`, `cloning`). Range: 2–300. Polling stops automatically once the realm settles. |
95+
| `b2c-dx.telemetry.enabled` | `true` | Send anonymous usage telemetry. Honors VS Code's `telemetry.telemetryLevel` — disabling that disables this regardless of this setting. |
96+
97+
### Complete defaults (copy-paste)
98+
99+
```jsonc
100+
// .vscode/settings.json
101+
{
102+
"b2c-dx.features.sandboxExplorer": true,
103+
"b2c-dx.features.webdavBrowser": true,
104+
"b2c-dx.features.contentLibraries": true,
105+
"b2c-dx.features.codeSync": true,
106+
"b2c-dx.features.logTailing": true,
107+
"b2c-dx.features.scaffold": true,
108+
"b2c-dx.features.apiBrowser": true,
109+
"b2c-dx.features.cap": true,
110+
"b2c-dx.logLevel": "info",
111+
"b2c-dx.sandbox.pollingInterval": 10,
112+
"b2c-dx.telemetry.enabled": true
113+
}
114+
```
115+
116+
## Next Steps
117+
118+
- [Overview](./) — what the extension can do.
119+
- [Authentication Setup](../guide/authentication) — Account Manager API clients, WebDAV access keys, OAuth scopes.
120+
- [CLI Configuration](../guide/configuration) — full `dw.json` reference and precedence rules.

0 commit comments

Comments
 (0)