Skip to content

Update 2026 theme names#291659

Merged
mrleemurray merged 1 commit intomainfrom
mrleemurray/vocational-amethyst-meadowlark
Jan 29, 2026
Merged

Update 2026 theme names#291659
mrleemurray merged 1 commit intomainfrom
mrleemurray/vocational-amethyst-meadowlark

Conversation

@mrleemurray
Copy link
Copy Markdown
Contributor

Revise theme IDs and labels to ensure consistency across the application.

2026 Light / Dark -> VS Code Light / Dark

This change enhances clarity and aligns with standard naming conventions. Testing can be done by verifying the updated themes in the settings.

Copilot AI review requested due to automatic review settings January 29, 2026 16:36
@mrleemurray mrleemurray enabled auto-merge January 29, 2026 16:36
@mrleemurray mrleemurray self-assigned this Jan 29, 2026
@vs-code-engineering vs-code-engineering bot added this to the January 2026 milestone Jan 29, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the theme IDs and labels for the experimental 2026 themes to improve clarity and naming consistency.

Changes:

  • Theme IDs changed from 2026-light-experimental / 2026-dark-experimental to Experimental Light / Experimental Dark
  • Theme labels changed from 2026 Light / 2026 Dark to VS Code Light / VS Code Dark

Comment on lines +20 to +21
"id": "Experimental Light",
"label": "VS Code Light",
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The theme label "VS Code Light" may be confusing for users because:

  1. There are existing themes with similar names: "Visual Studio Light" (ID: "Visual Studio Light") and "Light (Visual Studio)" are already present in the theme-defaults extension
  2. "VS Code" and "Visual Studio" are different products, which could cause user confusion
  3. The extension itself is named "2026 Themes" (theme-2026), making "VS Code Light" inconsistent with the extension's identity

Consider using a label that better reflects the extension name, such as "2026 Light" or a more distinctive name that doesn't overlap with existing themes.

Copilot uses AI. Check for mistakes.
Comment on lines +26 to +27
"id": "Experimental Dark",
"label": "VS Code Dark",
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The theme label "VS Code Dark" may be confusing for users because:

  1. There are existing themes with similar names: "Visual Studio Dark" (ID: "Visual Studio Dark") and "Dark (Visual Studio)" are already present in the theme-defaults extension
  2. "VS Code" and "Visual Studio" are different products, which could cause user confusion
  3. The extension itself is named "2026 Themes" (theme-2026), making "VS Code Dark" inconsistent with the extension's identity

Consider using a label that better reflects the extension name, such as "2026 Dark" or a more distinctive name that doesn't overlap with existing themes.

Copilot uses AI. Check for mistakes.
{
"id": "2026-light-experimental",
"label": "2026 Light",
"id": "Experimental Light",
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description states the change is from "2026 Light / Dark" to "VS Code Light / Dark" but doesn't mention that the theme IDs are also being changed from "2026-light-experimental" / "2026-dark-experimental" to "Experimental Light" / "Experimental Dark".

Theme IDs are what users reference in their settings (e.g., "workbench.colorTheme": "Experimental Light"), so changing them is a breaking change for anyone who has already configured these themes in their settings. The PR description should clearly document this breaking change.

Copilot uses AI. Check for mistakes.
@mrleemurray mrleemurray merged commit 16ef2c1 into main Jan 29, 2026
28 checks passed
@mrleemurray mrleemurray deleted the mrleemurray/vocational-amethyst-meadowlark branch January 29, 2026 17:10
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Mar 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants