Simplify and persist PowerShell session configuration changes #881
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change improves our session menu so that when the user selects a different PowerShell version the choice is persisted in their user settings. The previous code for managing session configurations has been mostly removed because it was unnecessarily complex. We've also added a new "powershell.powerShellExePath" setting to replace the now deprecated "powershell.developer.powerShellExePath" setting since this is now a user-level setting. If a user has the deprecated setting in their configuration file, we will notify them and fix it automatically if they wish.
8ca5548 to
dc119bc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change improves our session menu so that when the user selects a
different PowerShell version the choice is persisted in their user
settings. The previous code for managing session configurations has
been mostly removed because it was unnecessarily complex.
We've also added a new "powershell.powerShellExePath" setting to replace
the now deprecated "powershell.developer.powerShellExePath" setting
since this is now a user-level setting. If a user has the deprecated
setting in their configuration file, we will notify them and fix it
automatically if they wish.