Improve Settings Editor experience in a few places #3919
Merged
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.
PR Summary
This PR is two commits:
two low hanging fruits that allow the

CommandExplorerExcludeFilter
andfeatureFlags
settings to show up in the settings editor:a reworking of the

powerShellAdditionalExePaths
to be an object of{ [versionName: string]: "exePath" }
so that the user has a nicer experience in the settings editor. It's not perfect (I wish theItem
andValue
headers could be renamed), but it's the best we can do with the settings API today and think it's worth it.This also lights up nice things like this:

jumping to this:

PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
x
between the square brackets.Please mark anything not applicable to this PR
NA
.WIP:
to the beginning of the title and remove the prefix when the PR is ready