Skip to content

Fix settings grouping under PowerShell heading with subgroups in VS Code 1.101+ #5329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

Fix settings grouping under PowerShell heading with subgroups in VS Code 1.101+ #5329

wants to merge 4 commits into from

Conversation

Copy link
Contributor

Copilot AI commented Nov 21, 2025 •
edited
Loading

PR Summary

VS Code 1.101+ requires the id property in configuration objects to properly scope settings subgroups under an extension's heading. Settings groups (Interface, Formatting, Editor Services, Pester, Terminal, Developer) were appearing as separate top-level items instead of under the PowerShell extension heading.

Changes

Added id property to each configuration section in package.json to properly scope them under the PowerShell extension while preserving the title property for subgroup display names:

Before:

"configuration": [
  { "title": "Interface", "properties": {...} },
  { "title": "Formatting", "properties": {...} },
  // ... 4 more titled sections
]

After:

"configuration": [
  { "id": "powershell.interface", "title": "Interface", "properties": {...} },
  { "id": "powershell.formatting", "title": "Formatting", "properties": {...} },
  // ... 4 more sections with id and title
]

VS Code now groups all settings under the extension's displayName ("PowerShell") as the parent heading, with each titled section appearing as a subgroup.

Expected Settings UI Structure

PowerShell (parent heading)
  ├── Interface (subgroup - 11 settings)
  ├── Formatting (subgroup - 20 settings)
  ├── Editor Services (subgroup - 14 settings)
  ├── Pester (subgroup - 4 settings)
  ├── Terminal (subgroup - 7 settings)
  └── Developer (subgroup - 9 settings)

Impact

  • All 65 settings retain their IDs and behavior
  • Settings UI organization corrected for VS Code 1.101+
  • Subgroup organization preserved with clean titles
  • No breaking changes

PR Checklist

  • PR has a meaningful title
  • Summarized changes
  • [NA] PR has tests
  • This PR is ready to merge and is not work in progress

Fixes #5328

Original prompt

This section details on the original issue you should resolve

<issue_title>Settings Groups are no longer Grouped Under PowerShell Settings</issue_title>
<issue_description>
Type: Bug

Not sure when this happened but it appears our settings groups like "Interfaces", etc. no longer are under a general "PowerShell" dropdown. Need to review release notes for what changed and guidance to fix it.

Image

Extension version: 2025.4.0
VS Code version: Code 1.106.2 (1e3c50d64110be466c0b4a45222e81d2c9352888, 2025-11-19T16:56:50.023Z)
OS version: Windows_NT x64 10.0.26200
Modes:

System Info
Item Value
CPUs AMD Ryzen 7 6800U with Radeon Graphics (16 x 2695)
GPU Status 2d_canvas: enabled
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.19GB (2.99GB free)
Process Argv --crash-reporter-id 3452258d-3038-4ea2-ad58-b8b0ab2fa1bb
Screen Reader no
VM 0%
A/B Experiments 
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
aj953862:31281341
nes-set-on:31340697
6abeh943:31336334
envsdeactivate2:31353495
aa_t:31379598
t123456:31413567
gaj49834:31404438
cloudbuttont:31379625
todos-1:31405332
qwen_all_req:31402696
control_gpt5applypatchexclusively:31412085
3efgi100_wstrepl:31403338
trigger-command-fix:31379601
auto_model_enabled:31385282
use-responses-api:31390855
defaultusage:31403421
auto_g2946222:31414244
je187915:31401254
3i15c187:31419927
ec5jj548:31422691
nes-cd-200-200:31410880
copilot-nes-oct-t:31418199
c0683394:31419495
3fia6346:31423209

<agent_instructions>Review the latest vscode release notes, and fix the settings so they are all under a general PowerShell heading in the extension settings section</agent_instructions>

Comments on the Issue (you are @copilot in this section)

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@JustinGrote
Copy link
Collaborator

JustinGrote commented Nov 21, 2025

@copilot preserve the title property to be present, so that settings are still grouped by their extension name "PowerShell" but also in sub groups such as "Interface", but ensure they are all under the parent PowerShell header.

Copilot AI changed the title [WIP] Fix settings groups not appearing under PowerShell settings Fix settings grouping under PowerShell heading in VS Code 1.101+ Nov 21, 2025
Copilot AI requested a review from JustinGrote November 21, 2025 21:46
Copilot finished work on behalf of JustinGrote November 21, 2025 21:46
Copy link
Contributor Author

Copilot AI commented Nov 21, 2025

@copilot preserve the title property to be present, so that settings are still grouped by their extension name "PowerShell" but also in sub groups such as "Interface", but ensure they are all under th...

Done! Added id property to each configuration section (e.g., powershell.interface) and restored the original clean titles ("Interface", "Formatting", etc.) in commit 8375f70.

This properly scopes the subgroups under the PowerShell extension heading while maintaining the categorical organization you requested.

Copilot AI changed the title Fix settings grouping under PowerShell heading in VS Code 1.101+ Fix settings grouping under PowerShell heading with subgroups in VS Code 1.101+ Nov 21, 2025
Copilot finished work on behalf of JustinGrote November 21, 2025 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JustinGrote JustinGrote Awaiting requested review from JustinGrote

At least 1 approving review is required to merge this pull request.

Assignees

@JustinGrote JustinGrote

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Settings Groups are no longer Grouped Under PowerShell Settings

2 participants

@JustinGrote