Skip to content

Rebrand: extension name and UI strings #1027

Closed

Description

Part of #1024. Step 3, after the naming guidance and the Marketplace check.

Conservative change: in the UI the extension is "DocumentDB", like the activity bar, the command category and the terminal tabs already are. All new strings are the same length or shorter.

# Where Today New
1 package.json displayName DocumentDB for VS Code DocumentDB
2 Walkthrough title (package.json) Get Started with DocumentDB for VS Code Get Started with DocumentDB
3 Output channel (src/extension.ts) DocumentDB for VS Code DocumentDB
4 Release-notes prompt (releaseNotesNotification.ts) DocumentDB for VS Code has been updated. View the release notes? The DocumentDB extension has been updated. View the release notes?
5 Tenant errors (newConnection/ and updateCredentials/PromptTenantStep.ts) ...See the DocumentDB for VS Code output for details. ...See the DocumentDB output for details.
6 Account picker detail (SelectAccountStep.ts) DocumentDB for VS Code is not signed in to Azure Not signed in to Azure
7 Add connection from registry (addConnectionFromRegistry.ts) ...in the "DocumentDB for VS Code" extension... ...in the DocumentDB extension...
8 Azure Workspace "has moved" message (SwitchToDocumentDbItem.ts) ...moved to the "DocumentDB for VS Code" extension Full name, shown to users who need to find the extension
9 Survey card (SurveyInvitationView.ts and its test) DocumentDB for VS Code / How satisfied are you with DocumentDB for VS Code? / You've used DocumentDB for VS Code on {0} days... DocumentDB / How satisfied are you with the DocumentDB extension? / You've used the DocumentDB extension on {0} days...
10 API errors and JSDoc (api/src/utils/getApi.ts) DocumentDB for VS Code API DocumentDB extension API
11 Shell productName (packages/documentdb-js-shell-runtime, playgroundWorker.ts) DocumentDB for VS Code... Keep: client metadata, not branding; changing it needs a package release

Also:

  • package.json keywords: add "DocumentDB for VS Code" and "DocumentDB extension" so Marketplace search still finds us.
  • Update build/verification/activation/activation.test.cjs (4 log paths use the output channel name).
  • npm run l10n. Changed keys show English until the next localization drop.
  • Coordinate #9 wording with the Customer Voice survey issue so the satisfaction question stays comparable.
  • npm run lint, tests, and check the walkthrough, output channel and survey card in a dev build.

Activity

  1. added 3 commits that reference this issue on Oct 19, 2026
    cd5f4aa
    7c13381
    12a5b99
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions