-
Notifications
You must be signed in to change notification settings - Fork 39.1k
Display registered settings groups by extension #126089
Copy link
Copy link
Closed
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release noteson-testplansettings-editorVS Code settings editor issuesVS Code settings editor issues
Milestone
Metadata
Metadata
Assignees
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesIssue/pull request mentioned in release noteson-testplansettings-editorVS Code settings editor issuesVS Code settings editor issues
The
"configuration"extension contribution point can take a single object of setting keys -> definitions or an array of these, each with their own title. Currently the Extensions node in the settings editor TOC shows extension settings by config section with the registered title, mixed up globally and sorted alphabetically. A couple issues with this:So I'm thinking we should actually have the extension name as the top node, put the extension sections under that with their given titles and order. This actually makes extension sections much more useful. This is a good start towards giving extensions more control over the presentation of their settings, like discussed in #70589, and we don't have to extend JSON schema to do it.