Clear the 0.10.0 release blockers: drop the footer experiment, finish the rename, cut -alpha - #883
Merged
Tomasz Naumowicz (tnaum-ms) merged 6 commits intoAug 14, 2026
Conversation
Guanzhou Song (guanzhousongmicrosoft)
requested a review
from a team
as a code owner
August 11, 2026 16:38
Copilot started reviewing on behalf of
Guanzhou Song (guanzhousongmicrosoft)
August 11, 2026 16:38
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Removes a shipped webview “footer experiment” prototype, completes the “Set up DocumentDB Local” rename across user-facing product strings (including the OutputChannel name), and bumps the extension version to 0.10.0 for the release/0.10.0 cut.
Changes:
- Removed the footer experiment UI (switch/badge/styles) and simplified footer elevation measurement logic in both affected webviews.
- Updated user-facing strings to consistently use “Set up DocumentDB Local” and renamed the OutputChannel to “DocumentDB Local Setup”.
- Dropped the
-alphasuffix by setting the extension version to0.10.0and updating localization/docs accordingly.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/webviews/documentdb/localQuickStart/LocalQuickStart.tsx | Removes footer experiment UI/state/refs and keeps simplified footer elevation behavior; updates a few guidance strings. |
| src/webviews/documentdb/atlasCredentials/AtlasCredentialsView.tsx | Removes the same footer experiment UI/state/refs and keeps simplified footer elevation behavior. |
| src/services/localQuickStart/quickStartMessages.ts | Updates user-facing log guidance text from “Quick Start” to “DocumentDB Local setup”. |
| src/services/localQuickStart/ContainerRuntime.ts | Renames the OutputChannel to “DocumentDB Local Setup” and updates the related header comment. |
| src/commands/newLocalConnection/ExecuteStep.ts | Updates the modal detail text to reference “DocumentDB Local setup”. |
| src/commands/localQuickStart/localQuickStartCommands.ts | Updates user-facing messages to direct users to “Set up DocumentDB Local”. |
| package.json | Sets extension version to 0.10.0 and renames the command title to “Set up DocumentDB Local”. |
| l10n/bundle.l10n.json | Removes footer experiment strings and updates “Quick Start” user-facing strings to the new naming. |
| docs/user-manual/local-quick-start.md | Updates documentation to the new OutputChannel name. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The "Footer experiment" switch and its PREVIEW badge were a temporary comparison prototype, marked for removal in the code that added them. They shipped in the production bundle: `dist/views.js` built with `--mode production` carried the label, and the switch rendered in the installed VSIX in both the DocumentDB Local setup and the Atlas credentials wizard. The switch was absolutely positioned in the header, so it also overlapped the adjacent heading and truncated it at normal panel widths — "Add a Mongo", "Provide your MongoDB Atla", "Choose an authentication m". Remove the opt-in state, the root and footer refs, the prototype switch and badge, and the scrollAreaInlineFooter style. The measurement callback stays, minus the experiment: it still drives `footerElevated`, the shipped border-and-shadow that appears only while the scroll area has content below the fold. With the experiment gone `shouldDock` was always true, so the docked branch is the only one left. The ResizeObserver now watches the scroll area and content; the scroll area resizes when the footer does, so observing the root and footer added nothing. `position: relative` stays on the root — it is the containing block for the visually-hidden status text — with a comment that says so.
…the docs
The rename reached the user manual but no product string, so the feature
answered to two names at once. The Command Palette still offered "DocumentDB:
Local Quick Start" — a name that appeared nowhere else in the UI — and ten
user-facing strings still said "Quick Start", including two that sent the
reader to a log by a name the Output panel did not use.
- Command Palette title becomes "Set up DocumentDB Local", matching the tree
action that opens the same webview.
- The ten strings now name either the command ("Set up DocumentDB Local") or
the product ("DocumentDB Local"), whichever the sentence is about.
- The OutputChannel becomes "DocumentDB Local Setup", so "Check the DocumentDB
Local setup logs" names a channel that exists. The user manual follows.
The tree keeps "Your own DocumentDB" as its section heading and the webview
keeps "DocumentDB Local" as its title: those name the place and the product,
not the command, and are deliberate. Internal identifiers (localQuickStart,
QUICK_START_*) are untouched — renaming them is churn with no user-visible
effect.
Drop the -alpha prerelease suffix: the marketplace build must carry the final version.
The release cut had no changelog entry: CHANGELOG.md still opened at 0.9.2 while package.json said 0.10.0, so a release carrying two headline features would have shipped with no user-facing record of what changed. Written from the 25 PR-titled commits in v0.9.2..release/0.10.0, in the existing house style. Grouped as New Features (DocumentDB Local, MongoDB Atlas Service Discovery, Index Management), Improvements (theme-aware Fluent colors, typed status reporting) and Fixes (the bug-bash batch, Collection View import/export). No Security section: unlike 0.9.2 there are no dependency or GitHub Actions updates in this range. Four commits in the range carry fork-local PR numbers (#1, #3, #7, #8) that do not resolve in this repository; their substance is folded into the DocumentDB Local and bug-bash entries without links. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The version bump set package.json to 0.10.0 but left the lockfile at 0.10.0-alpha in both `.version` and `packages[""].version`, so the cut was only half applied. Only those two fields change — no dependency resolution ran, so the diff stays at two lines and the resolved tree is untouched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Guanzhou Song (guanzhousongmicrosoft)
force-pushed
the
dev/guanzhousong/0.10.0-release-blockers
branch
from
August 12, 2026 17:32
1d28dae to
24be061
Compare
Contributor
✅ Code Quality Checks
This comment is updated automatically on each push. |
Contributor
📦 Build Size Report
Download artifact · updated automatically on each push. |
Tomasz Naumowicz (tnaum-ms)
approved these changes
Aug 14, 2026
Tomasz Naumowicz (tnaum-ms)
deleted the
dev/guanzhousong/0.10.0-release-blockers
branch
August 14, 2026 15:56
github-project-automation
Bot
moved this to Done
in DocumentDB for VSCode: Release Plan
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clears the release blockers I raised in my review of #820, so that PR can go to the marketplace once this lands. Targets
release/0.10.0.Found by installing the packaged VSIX rather than using F5 — per the warning in
docs/ai-and-plans/PRs/766-webview-ext-package-redesign/webview-ext-review.mdthat the dev flow serves webview assets from the webpack dev server while a packaged build loads them off disk.1. Remove the footer experiment user-test prototype
The "Footer experiment · PREVIEW" switch was a temporary comparison prototype. The code that added it marked it for removal:
It was not dev-only.
dist/views.jsbuilt with--mode productioncarried the label, and the switch rendered in the installed VSIX in both the DocumentDB Local setup and the Atlas credentials wizard.It was also not cosmetic. Absolutely positioned in the header, it overlapped the adjacent heading and truncated it at normal panel widths:
Add a MongoProvide your MongoDB AtlaChoose an authentication mRemoved: the opt-in state, the root and footer refs, the switch and badge, the
scrollAreaInlineFooterstyle, and the now-unusedBadge/Switchimports.Kept — the measurement callback still drives
footerElevated, the shipped border-and-shadow that appears only while the scroll area has content below the fold. With the experiment goneshouldDockwas alwaystrue, so the docked branch is the only one left. TheResizeObservernow watches the scroll area and content: the scroll area resizes when the footer does, so observing the root and footer added nothing.position: relativestays on the root as the containing block for the visually-hidden status text, now with a comment saying so.2. Finish the rename in the product, not just the docs
45bdf28brenamed things in the user manual but touched no product string, so the feature answered to two names at once."Set up DocumentDB Local"appeared zero times inpackage.json.DocumentDB: Local Quick Start→DocumentDB: Set up DocumentDB Local, matching the tree action that opens the same webview.l10n/bundle.l10n.jsonsaid "Quick Start". Each now names either the command or the product, whichever the sentence is about.grep -c "Quick Start"on the bundle is now0.DocumentDB Local Quick Start→DocumentDB Local Setup, so "Check the DocumentDB Local setup logs" names a channel that actually exists. The user manual follows.Deliberately unchanged: the tree keeps Your own DocumentDB as its section heading and the webview keeps DocumentDB Local as its title — those name the place and the product, not the command. Internal identifiers (
localQuickStart,QUICK_START_*) are untouched; renaming them is churn with no user-visible effect.3. Version →
0.10.0Dropped the
-alphasuffix.Still outstanding on #820 — not fixable here
The
[WIP]prefix in #820's title. That is a field on the PR itself, so it needs an edit there, not a commit here.Verification
tsc --noEmitclean;eslint --quietclean;prettier -cclean.npm run l10nregenerated; bundle has 0 remaining "Quick Start" strings.dist/views.js(production mode):Footer experiment4 → 0 occurrences,scrollAreaInlineFooter0.extension/package.jsoninsidevscode-documentdb-0.10.0.vsix:version: 0.10.0, and the command title readsSet up DocumentDB Local.One check still open: I have not re-driven the rebuilt VSIX through the UI to eyeball the two webviews — my browser harness wedged before I got to it. The removal is verified at the bundle level and the full test suite is green, but a quick manual look at the DocumentDB Local setup and Atlas wizard (headings render in full; footer border/shadow appears only when content runs below the fold) is worth doing before merge.
Note on how this was produced
Written with AI assistance (Claude Code): I drove the packaged-VSIX smoke test, and the diagnosis, edits and commit messages were produced with it under my review. The verification results above are from real runs, not estimates.